11 results found
-
Ensure “Success” build status means the environment is ready
In Shopware Native PaaS, a build from a commit SHA can sometimes show as “Success” even though the environment isn’t actually accessible and returns a 404 error. This causes downtime and confusion. The build process should only mark a build as “Success” once the environment is fully functional.
2 votes -
Check plugin compatibility before updates in Shopware Native PaaS
Unlike self-hosted Shopware, Shopware Native PaaS doesn’t show whether installed plugins are compatible with the next Shopware version before updating. This forces manual checks — and internal plugins can’t be checked at all. A compatibility check tool in sw-paas or a dashboard would save time and reduce update risks.
2 votes -
Support cron jobs per application in Shopware Native PaaS
Some business processes (like product imports) need automated scripts to run on a schedule. Shopware Native PaaS should support cron jobs per application, ideally managed through sw-paas.
2 votes -
Allow application updates without logging all Admin users out
Updating an application in Shopware Native PaaS currently forces all Admin users to log out, interrupting work. Updates should be possible without logging everyone out.
2 votes -
Allow SSH or SFTP access to applications
Debugging plugins and themes in Shopware Native PaaS would be much easier if developers could connect directly to files and the database via SSH or SFTP.
2 votes -
Provide a GUI for non-technical tasks in Shopware Native PaaS
Not everyone is comfortable using sw-paas commands for everyday tasks. A simple dashboard for creating apps, cloning environments, etc would make Shopware Native PaaS easier to use for less technical users.
2 votes -
Shorten and simplify the sw-paas build history display
The build history in sw-paas grows very long, making it hard to find the latest entry. By default, show only the most recent few builds with an option to expand the full history. Clear formatting and a summary line like “Latest build: SUCCESS at 14:35” would make it much easier to read.
2 votes -
Command to fully clone an environment in sw-paas
Setting up a new staging or testing environment in Shopware Native PaaS is slow because everything has to be reinstalled and reconfigured manually. A single sw-paas command could copy the database, settings, and plugins from an existing environment in one step, saving significant time.
2 votes -
Make it easy to hide deleted apps in sw-paas
Right now, the sw-paas list shows apps that have already been deleted. This clutters the view and makes it harder to find what’s actually active. It would be great if deleted apps were either hidden or clearly marked so they’re easy to ignore.
2 votes -
Show only compatible updates in composer outdated
The composer outdated command lists updates even if they aren’t compatible with the current Shopware version. It would be more useful if it only showed updates that can actually be applied.
1 vote -
Show which plugins have updates in the Admin
When the “Extension updates are available” popup appears in the Admin, it’s unclear which plugins need updating. The affected plugins should be listed directly in the Admin.
1 vote
- Don't see your idea?