Staging Manager
Deutsch Demo shop View in the StoreStore

Manual All settings.

The plugin configuration applies to all staging environments together. You find it under Extensions › Staging Manager › Settings. What applies per staging environment is on its page.

Access

FieldDefaultEffect
Reachable without password fromemptyIP addresses or ranges, one per line, such as the office or a monitoring service. They get into every staging environment without the password page; a change applies at once, in built ones too.
Login lasts (days)30This long a visitor stays logged in after the password; a direct link lasts as long.

Mails

FieldDefaultEffect
Catch-all address for mailsemptyEvery mail goes here with "Everything to one catch-all address" if the staging environment has none of its own. Empty: mails are only archived.
Subject prefix[STAGING]Put in front of the subject of every mail a staging environment delivers. Empty: no prefix.

When building

FieldDefaultEffect
Mark usage data as declined in staging environmentsonEnters "declined" while setting up: no window in the copy, no data to Shopware.

Leave out directories

FieldDefaultEffect
Create empty, do not copy the contentsvar/cache, var/log, var/queue, var/lockThe folder is created empty. With a slash an entry counts from the live shop directory, without one it matches everywhere.
Leave out completely.git, .github, .idea, .vscode, node_modulesNeither folder nor content comes along. The staging folder and every staging environment with a path of its own always stay out.

Leave out files

FieldDefaultEffect
File names, exactly as writteninstall.lock, .env.local.phpOne name per line, no wildcards; without a slash wherever it sits.
File patterns with wildcards*.sql, *.sql.gz, *.zip, *.tar, *.tar.gzOne pattern per line; patterns apply to files only.

Comparison

FieldDefaultEffect
Exclude table contentsLog, queue and session tables such as log_entry, messenger_messages, cartExact table names; only contents are skipped, the structure is still compared.
Exclude directoriespublic, var, vendor, files/mediaNeither folder nor content is compared. Changed packages still show through composer.json and composer.lock.

Automation

FieldDefaultEffect
Carry runs in the backgroundonStarts runs from the schedule and continues runs whose window was closed. Off: runs only while the window is open.
Remind before a staging environment expiresonReports an event for the Flow Builder 7 days and 1 day before the expiry.
Allow the console commandsonOff: every command with the prefix dvsn-staging: stops before it does anything.

Protocols

FieldDefaultEffect
Detail of the run protocolEvery step"Errors only", "Errors and warnings", "Every step" or "Every slice", the last only for tracing a fault.
Keep run protocols for days30After that a scheduled task deletes the protocol; the run stays in the list. At most 180 days.
Keep anonymization records for days90After that a scheduled task deletes the records. 0 keeps them forever.

Performance

FieldDefaultEffect
Slice size in megabytes4How much data one portion moves. Smaller spares a busy live shop, larger finishes sooner.
Seconds per request in the admin10How long one request of the run window works. Lower it if the server cuts requests off early.
Seconds per background run50How long the scheduled task works per turn, shared between all open runs.
Runs at the same time3How many staging environments may be built at the same time; 0 without a limit. Above that a run waits.

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:What gets copiedEmails and callsSchedule and automation

More chapters