Skip to main content Skip to search Skip to main navigation
Shopware Payments ramp-up pricing for 12 months. Limited time only. Learn more
Diese Seite ist auch auf Deutsch verfügbar.
weedesign

Staging Environment Manager

Rating: 5.0

Average rating of 5 out of 5 stars

(1 reviews)
Downloads: <10

Description

Highlights

  • Staging environment in a subdirectory of your shop, with its own database
  • Automatic pre-flight check and optional DB test for each new staging environment
  • Choose the staging data: media, customers and orders can be left out
  • Live progress and log while the staging copy is created, without SSH
  • Sync the staging environment from the live shop with one click

Features

  • Create the staging database automatically or use an existing empty one
  • Current DB credentials and password taken over for the staging database
  • Staging database password stored encrypted with AES-256-GCM
  • Carts, logs and message queue land empty in the staging copy
  • Own exclude patterns for files you do not need in the staging copy
  • Sales channel domains rewritten to the staging URL
  • Staging .env with its own database URL, APP_URL and a new APP_SECRET
  • Elasticsearch/OpenSearch search switched off in the staging copy
  • STAGING badge and Administration bar in the new staging copy (until a sync)
  • noindex, nofollow for the new staging storefront (default, until a sync)
  • Staging files copied in batches of 2,000 with automatic retries
  • nginx location block for the staging subdirectory, also as a file
  • Several staging environments side by side
  • Status, last sync and (when ready) duration on each staging card
  • Delete a staging environment with its database (or tables), files and symlink

About the Extension

Staging environment in a subdirectory of your shop

The Staging Manager copies your shop with files and database into a subdirectory such as yourdomain.com/staging. Each staging environment gets its own database, and you create, sync and delete it in the Administration under Settings > Staging Manager. Files are copied with PHP and the database is cloned table by table, so creating and syncing the copy needs no SSH access and no command line; with nginx, you add one location block to your server configuration.

Pre-flight check for the staging environment

Before you create a staging environment, the plugin checks your server:

  • Project, public and var directories (writable)
  • .env file (readable)
  • Free and total disk space
  • PHP extensions pdo_mysql, openssl, json and mbstring
  • Connection to the production database
  • Symlink support (on servers other than Apache)

Database for the staging environment

  • Created automatically if it does not exist yet; alternatively, you use an existing empty database
  • "Use current DB credentials" fills in host, port and user of your shop's database
  • Optional: "Use current DB password" loads the password from the server
  • "Test DB connection" checks the connection and whether the database is empty or can be created
  • The database user needs the rights SELECT, INSERT, UPDATE, DELETE, CREATE, DROP and ALTER for the staging database, on MySQL also REFERENCES
  • The password of the staging database is stored encrypted (AES-256-GCM)

Data and files for the staging copy

  • Media, customers and orders are included by default; if you leave them out, their tables are created without content
  • Carts, logs, message queue and tokens: tables without content
  • Files: .git, .github and node_modules in the shop root and var/cache, var/log, var/queue and var/lock are always left out
  • Your own exclude patterns, for example public/uploads/large
  • Other staging environments are never copied into a new one
  • Database views are skipped and named in the log

Staging setup with progress and log

  • Four steps: copy files, set up the database, rewrite the .env, write the web server configuration
  • Progress bar and live log in the Administration
  • Small batches: 2,000 files per request, large tables in chunks
  • On gateway errors (502, 503, 504) the request is retried automatically
  • After an error the environment is kept for troubleshooting; "Retry" runs a sync (files, database, .env), deleting removes it

What changes in the staging copy

  • Sales channel domains point to the staging URL, for example yourdomain.com/staging/en
  • .env with the staging database, APP_URL and a new APP_SECRET
  • Elasticsearch/OpenSearch search off (SHOPWARE_ES_ENABLED=0); other Elasticsearch settings such as indexing keep the values of your live .env
  • MAILER_DSN=null://null; mailer settings saved in the Administration, such as SMTP, take precedence and are copied, so the copy can still send e-mails
  • .env files set to 0600 and blocked for web requests
  • Cache of the copy cleared
  • On creation, the copy gets the Staging Indicator plugin: an orange "STAGING" badge in the storefront, a "STAGING ENVIRONMENT" bar in the Administration and noindex, nofollow (default, can be changed in the copy); after a sync, the indicator and noindex are no longer active

Apache and nginx for your staging environment

  • A symlink public/staging leads to the public folder of the copy
  • Apache: on creation, the copy gets an .htaccess with the matching RewriteBase
  • nginx: the "Create Staging Environment" page shows the location block for your server block, with the detected PHP-FPM target (fastcgi_pass); during setup it is also saved as config/nginx-staging-[subdirectory].conf.example

Sync, logs and deleting the staging environment

  • "Sync" copies files and database from the live shop again and overwrites them in the staging copy; files and tables that exist only in the copy are kept
  • Each card shows status, directory, database and last sync; ready environments also show the duration
  • "Shop" and "Admin" open the staging storefront and its Administration
  • Logs for every staging environment, with optional auto-refresh
  • "Reset stuck status" for a process that no longer runs
  • Deleting removes the staging database (or its tables), the files and the symlink
  • Several staging environments side by side, each with its own subdirectory and database

Details

  • Available: English, German
  • Latest update: 2 November 2026
  • Publication date: 3 July 2026
  • Version: 2.0.3
  • Category: Administration

Resources

Reviews (1)

Average rating
5.0

Average rating of 5 out of 5 stars

Based on 1 reviews
5.0 Functionality
5.0 Usability
5.0 Documentation
5.0 Support

100 %
0 %
0 %
0 %
0 %

Write a review

If you downloaded this extension you can write a review in the Shopware Account.

Write a review
Einfach einzurichten und hervorragender Support!
5.0

Average rating of 5 out of 5 stars

by Stefan Peil
3 November 2026 13:47
Das Staging-System für Shopware ist wirklich eine tolle Sache! Mit nur wenigen Klicks ist alles eingerichtet und man kann ganz in Ruhe Änderungen testen, ohne den laufenden Shop zu beeinflussen.

Besonders hervorheben möchte ich den super Support. Wenn mal etwas nicht auf Anhieb klappt oder Fragen auftauchen, ist er zur Stelle und hilft schnell, unkompliziert und vor allem sehr persönlich weiter. Man merkt einfach, dass ihm seine Kunden am Herzen liegen.

Vielen Dank, Wolfgang, für die tolle Unterstützung! Von uns gibt es eine ganz klare Empfehlung und 5 Sterne!
5.0 Functionality
5.0 Usability
5.0 Documentation
5.0 Support

About the Extension Partner

Partner Status

  • Shopware Extension Partner Shopware
    Extension Partner

Details

  • Ø-Rating: 4.9

    Average rating of 4.9 out of 5 stars

  • Partner since: 2019
  • Extensions: 71

Support

  • Based in: Germany
  • Speaks: German, English
  • Response time: Very quickly