Staging Manager

Manual Glossary.

What the words of the plugin mean, and which other words mean the same.

The words of the plugin.

Staging environment
A copy of the live shop for testing, with files, a database and an address of its own. Also called test system, test environment, test shop or development system.
Live shop
The shop customers buy in. The plugin only reads it; the copy is made from it and managed in it.
Build, rebuild
A run that copies files and database anew and sets the copy up. The first time the button says "Build staging environment".
Refresh data
A run that copies only the database anew; code, themes and media of the copy stay.
Tear down
Deletes files and database content of a staging environment; the settings stay. Only then can it be deleted from the list.
Run
Everything the plugin does to a staging environment: build, refresh, closing check, comparison, teardown. The preflight runs as the first step of every build and on its own in a window of its own.
Run window
The window that shows a run before, during and after, with progress, check results, protocol and settings.
Slice
A small, repeatable portion of a run. Because a run works in slices, it does not fail on the size of the shop and continues where it stopped.
Preflight
The check before a build: server, database, web server, space, services and anonymization. It changes nothing.
Closing check
The check at the end of a build: staging flag, addresses, banner, robots.txt, administration, media.
Self-test
The check inside the copy, run when its dashboard opens.
Staging folder
The folder staging inside the live shop's directory that holds the staging environments in a subdirectory.
Password page
The page in front of storefront, administration or both that asks for the password of the staging environment.
Default user
An administrator the plugin creates only in the copy, for an agency for instance.
Catch-all address
The one address that receives every mail of the copy with "Everything to one catch-all address".
Mail archive
The list of every mail the copy would send, in the copy's administration.
Rule set
The shared anonymization rules per table and column, for every staging environment.
Anonymization record
The proof of which columns a run replaced how, kept in the plugin's private storage.
Staging mode
Shopware's own staging flag: banner, mail lock, robots.txt. The command system:setup:staging sets it in a finished copy; the plugin sets it while setting up.
Comparison
A run that reads live shop and copy and lists what changed since the copy, on which side.
Lifetime
An expiry date after which the copy locks storefront, administration and API.

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:Comparison with the standardSetting up

More chapters