Manual Dashboard and list.
The dashboard shows every staging environment of this live shop at a glance: how many there are, which are ready, where a run is going on and which need attention. The list shows the same as a table.
Tiles at the top, a card per staging environment below.
- Staging environments
- Every staging environment of this live shop, built or not.
- Ready
- Built, up to date with the last run and not expired.
- Running now
- Staging environments with a run open right now.
- Needs attention
- Failed or expired; the card of the staging environment says what is wrong.
- Space in the staging folder
- What the staging environments take up together and how much is still free in the staging folder.
Each card shows name and status, address, "Data from", size and validity, and below at most one line: the progress of an open run, the failed run, the expiry or the next appointment of the schedule. The blue button names the next step; "Open staging environment" opens storefront or administration past the password page.
A card for what is not in the list.
The card only appears when the staging folder holds something that belongs to no staging environment of the list: a staging environment of this live shop no longer in the list, another Shopware installation, remains of another staging plugin or any other folder. You can delete each find; a staging environment of your own is torn down like any other, for everything else only the folder is deleted.
Overview › Environments.
In the sidebar on the right you filter by status and mode, in the search at the top by name.
| Column | What it shows |
|---|---|
| Name | What the staging environment is called; a click opens its page. |
| Status | Ready, Never built, Running (with progress), Failed or Expired. |
| Mode | Subdirectory or Own path. |
| Address | Where the staging environment answers; with a password page it asks for the password there. |
| Data from | The state of the live shop the copy has: the start of the last build or refresh. |
| Valid until | Until when the staging environment is valid; afterwards storefront, administration and API are locked. |
| Size | What the staging environment takes up in files and database. |
The same as on the cards of the dashboard.
- Edit
- Opens the page of the staging environment.
- Duplicate staging environment
- A new staging environment with the same settings, with a new name; schedule and default user are off.
- Rebuild
- The first time "Build staging environment": builds files and database completely anew.
- Refresh data
- Fetches only the database anew; the files stay.
- Preflight, closing check
- Check server and copy without changing anything.
- Open storefront, Open administration
- Open the staging environment in a new window, past the password page.
- Show credentials
- Addresses, passwords and default user to copy and pass on.
- Tear down staging environment
- Deletes files and database content; only then can it be removed from the list completely with "Delete staging environment".
Staging environments and their databases stay, even with "Remove all app data permanently". If you no longer need them, tear them down first.
What it is all for
The manual says where something sits in the administration. Why it is like that and what it brings day to day is explained on the topic pages.
More on this:Setting upWhat gets copied
More chapters
-
The page of a staging environment
The eight tabs of a staging environment, every field and what it does.
-
The run window
Confirmation, progress, check results, protocol and settings of a run.
-
Scheduler and anonymization
The scheduler with every schedule and the anonymization rule set.
-
Inside the staging environment
The dashboard of the copy, self-test, outgoing requests, mail archive and login.
-
All settings
Every field of the plugin configuration with default and effect.
-
Glossary
Staging environment, test system, run, slice, catch-all address and the other words of the plugin.