Create staging / testenvironments

by moori.media

Rating: 5.0

Downloads: 283

Create and delete a staging system with just one click? This plugin makes it possible! Thanks to high-performance processes on the core level, it is simple as possible.

Annually €22.50* /month €300.00 * €270.00* /year 10% discount In comparison to the regular monthly price

Monthly €25.00* /month Cancelable monthly

Compatible with:

6.4.0.0 - 6.7.16.0

Includes:

Free trial month

The subscription starts with a free trial month during which it can be canceled at any time.

All updates

During the subscription all released updates are included for free

Support from the Extension Partner

In case you have any questions or problems with your extension you can always ask the Extension Partner for help during the subscription.

Description

Highlights

Shopware test copies with a separate database and shop directory
Guided workflow with dashboard, checks and five creation steps
Configurable database and file exclusions per staging environment
Optional customer anonymization in defined destination tables
Four execution methods with local commands or SSH on the same server

Features

Manage multiple staging environments in Shopware Administration
Dashboard with internal notes and Storefront and Administration links
System check and database connection test before creation
Database backup and import using mysql and mysqldump
Content exclusions for customers, orders, carts and additional tables

File copying with rsync and configurable exclusion patterns
File permission, owner and group options
Symlink creation through PHP or shell with optional shared media
Destination database connection, app URL and sales channel domain mapping
Maintenance mode, dev mode and optional deactivation of all destination plugins
Configurable destination environment variables
Anonymize defined customer data and clear existing customer login credentials
PHP shell and Symfony Process locally or through SSH on localhost
SSH credentials from plugin configuration or server-side ENV variables
Progress display, individual step execution and configurable logging

Show more Show less

About the Extension

Test updates and changes in a staging shop first

MoorlStaging creates and manages test environments directly in Shopware Administration. A separate database and shop directory provide a place to test Shopware updates, extensions and configuration changes before applying them to production.

Three tabs guide the workflow: record the test purpose on the Dashboard, check the server and destination connection under System & database, then configure and start the copy under Create staging. Creation is enabled only after both checks pass.

Five steps with control over data and files

Creation runs through five clear steps: back up the database, import it into the destination database, copy shop files, create symlinks and configure the destination shop. Progress and status identify the current step; a reported step error stops the full run. Individual steps can be repeated when needed.

Exclude carts, log entries, orders, customers, SEO URLs and search keywords from the database export. Add further table names on separate lines. File exclusions with wildcards, cache and version-control options, and configurable permissions help adapt the copy to your server.

Prepare the destination for your tests

MoorlStaging sets the destination database connection, can update the app URL and maps sales channel domains to the staging path while preserving existing language paths and subpaths. Configure maintenance mode, development mode, deactivation of all plugins and your own list of environment variables to set or remove.

A successful full run returns you to the Dashboard with Storefront and Administration links. Internal notes help identify update tests, investigations and development environments.

Optional customer anonymization

When copying customers and orders for testing, step 5 can replace certain personal data in customer accounts, customer addresses, order customers and order addresses with test data. Customer/order relationships remain intact. The option is off by default and operates only on the destination database.

Existing customer passwords, legacy credentials and recovery records are cleared. Existing customer logins no longer work in staging afterwards. Documents, files, logs, reviews, newsletter data and other plugins' data are not anonymized; the SQL backup created beforehand is also unaffected. The scope is limited to the customer tables described.

Local commands or execution through SSH

Choose PHP shell, PHP shell via SSH, Symfony Process or Symfony Process via SSH. SSH connects to the same server on localhost:22. Credentials can come from plugin settings or server-side environment variables. The Symfony/OpenSSH variant also supports key authentication and checks the known host key.

Hosting profiles set binary paths and initial settings for new environments. Existing environments retain their individual settings. You can supply paths to mysql and mysqldump manually and select the logging level.

Requirements and operational notes

The extension targets Shopware 6.7 and requires a suitable server with executable shell tools including rsync, mysql, mysqldump and sed. Depending on the execution method, it requires exec, proc_open, the PHP ssh2 extension, or OpenSSH with sshpass for password authentication. Provide a separate destination database, sufficient storage, appropriate permissions and web server rules for the staging path. MoorlFoundation is not required.

Media is copied by default. If you exclude media and link it to the live shop, both shops share those files; changes or deletions in staging then affect the live shop too. Review mail transport, payment providers, webhooks and background services before testing.

The extension creates test copies; it does not automatically transfer changes back to the live shop. Imports and repeated steps can overwrite destination data. The deletion action attempts to remove destination database tables, the copy, backup and public symlink; verify the result. Uninstallation does not automatically remove existing test environments.

Available hosting profiles are not a blanket guarantee for hosting packages. Setup and duration depend on your server, data volume and web server configuration.

Test updates and changes in a staging shop first

Five steps with control over data and files

Prepare the destination for your tests

A successful full run returns you to the Dashboard with Storefront and Administration links. Internal notes help identify update tests, investigations and development environments.

Optional customer anonymization

Local commands or execution through SSH

Requirements and operational notes

Available hosting profiles are not a blanket guarantee for hosting packages. Setup and duration depend on your server, data volume and web server configuration.

This extension is highlighted as part of the Premium Partner Program and can therefore be displayed with priority in the store.

Details

Available: English, German
Latest update: 9 November 2026
Publication date: 29 April 2022
Version: 1.7.9
Category: Administration

Resources

Reviews (5)

Average rating

5.0

Based on 5 reviews

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

Write a review

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

Write a review

Sort by

Alles super - bestes Staging Plugin

5.0

by Mark A.

13 November 2025 11:22

Preis / Leistung unschlagbar - macht genau was es soll zu einem TOP PReis - Support beispiellos.

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

by moori.media 13 November 2025 12:11

Vielen Dank für die Bewertung und vor allem auch für die Tipps und Hinweise um das Plugin zu optimieren!

Tolles Plugin - toller Support

5.0

by Markus Engel

12 December 2024 20:41

Das Plugin macht genau, was es soll und erstellt Testumgebungen. Die Konfiguration war nicht ganz einfach im Zusammenspiel mit unserem Hoster all-inkl., aber Herr Georg von Moori hat schnell geholfen, bis es lief.

Jetzt gibt es in der Beschreibung auch entsprechende Infos zu verschiedenen Hostern. Von daher alles perfekt, gutes Plugin und guter Support, wir sind sehr zufrieden.

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

Erweiterung, Preis und Support 100% Zufriedenstellend

5.0

by Pierre Martin

2 May 2024 11:57

Ich nutze diese nützliche Erweiterung schon seit ein paar Monaten und was soll ich sagen, alles perfekt bei mir. Ich hatte nun auch schon 2 Anfragen beim Support von Moori und auch hier gibt es volle Punktzahl, da mir sofort weitergeholfen wurde. Außerdem hat mich im Vorfeld auch der Preis überzeugt, dieser lag noch in meinem Budget für solch eine Erweiterungen. Ich kann mich an dieser Stelle nur nochmals beim kompletten "Moori - Team" bedanken für die tolle Erweiterung.

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

Faires Preisleistungsverhältnis + sehr schneller Support!

5.0

by kontorplus.De

27 February 2024 14:45

Diese Erweiterung funktioniert einwandfrei bei Profihost (sogar uns ohne den in der Anleitung erwähnten Apache Neustart).

Die Installation/Grundeinrichtung war ebenso schnell und unkompliziert möglich.

Insgesamt findet man hier bei der Erweiterung "Test- und Stageumgebung" ein sehr faires Preisleistungsverhältnis (gegenüber Mitbewerbern) und der Support reagiert auch sehr schnell bei möglichen Fragen.

Vielen Dank und viel Erfolg weiterhin!

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

Great staging system

5.0

by Hanno-Christian Schulz

22 September 2023 17:52

Works like a charm and Moori's support is awesome.

5.0 Functionality

5.0 Usability

5.0 Documentation

5.0 Support

About the Extension Partner

moori.media

See all extensions

Partner Status

Shopware
Premium Extension Partner

Details

Ø-Rating: 4.6

Average rating of 4.6 out of 5 stars
Partner since: 2019
Extensions: 63

Support

Based in: Germany
Speaks: German, English
Response time: Quickly

Installation and operations

Requirements

MoorlStaging targets Shopware 6.7. Use PHP and database versions supported by your Shopware installation. MoorlFoundation is not required.

You need:

A server environment with a Unix shell and tools such as rsync, mysql, mysqldump, sed, touch and rm; depending on options, also ln, chmod and find.
The PHP functions, extensions and, where applicable, SSH tools required by your selected execution method.
Read access to the source shop, write access to _moorl_staging and the shop's public directory, and permission to create symlinks.
A dedicated destination database created beforehand, with credentials and sufficient permissions to import and, where needed, drop tables.
Enough storage for the SQL backup, database copy and shop files.
A valid source APP_URL and web server rules allowing the staging path and its symlinks.
PHP, web server and proxy runtime limits sufficient for your data volume. There is no fixed creation-time guarantee.

The system check assists with setup. It does not confirm universal hosting compatibility or complete isolation of every integration.

Installation

Back up the production shop and review server requirements.
Install and activate MoorlStaging under Extensions → My extensions.
Open the extension configuration and select command execution, SSH credentials where needed, and the hosting compatibility mode.
Open Settings → Extensions → Staging and create a staging record.
Pass the system and database checks, configure the five creation steps and start the full run.
Check the destination shop and external services before starting tests or background processes.

See Create staging / test environments for the complete guide with screenshots and options.

Command execution

Selection Execution Requirement PHP shell Locally as the PHP user PHP exec function PHP shell via SSH As the SSH user on localhost:22 PHP ssh2 extension, username and password Symfony Process Locally as the PHP user PHP proc_open function Symfony Process via SSH Through OpenSSH as the SSH user on localhost:22 proc_open, OpenSSH; password login additionally requires sshpass

New installations start with PHP shell. Updates migrate the previous SSH setting to the corresponding execution method. There is no separate SSH activation switch. SSH runs commands as another user on the same server; a configurable remote host is not provided.

For Symfony Process via SSH, the PHP user must already trust the localhost host key through known_hosts or a system-wide file. Unknown or changed host keys abort execution. An empty password uses key authentication through the PHP user's SSH configuration. Password authentication supplies the password to sshpass through the SSHPASS environment variable.

The Symfony variants do not impose a process timeout. PHP, web server and proxy runtime limits still apply. Error output is captured without rerunning failed commands to collect it.

SSH credentials from ENV

For both SSH variants, SSH credentials source selects Plugin configuration or Environment variables (ENV). Set ENV values on the server, for example in .env.local:

MOORL_STAGING_SSH_USERNAME=staging
MOORL_STAGING_SSH_PASSWORD='your-ssh-password'

Values are read only on the server and are not copied into plugin settings or displayed in Administration. The Administration fields are ignored in ENV mode; missing ENV values do not fall back to those fields. Clear credentials previously saved in Administration after switching so the old values no longer remain accessible through Administration.

Only Symfony Process via SSH supports an empty password for key authentication. PHP shell via SSH requires a password. ENV changes must take effect for the executing PHP process; also account for existing ENV dumps and service configuration.

Hosting compatibility mode, binary paths and logging

Select Hosting compatibility mode exclusively in the plugin configuration. It controls database binary paths and initial settings for new staging environments. Saved individual process settings are preserved when loading. There is no additional provider selector or load button in the staging screen.

Available profiles are Default, All-Inkl, Mittwald, Profihost (MariaDB / MySQL / MySQL 8), Timme Hosting (MySQL 8) and Manual input. A listed profile is not a guarantee for all hosting packages or server configurations. Check available tools, database versions, permissions and web server rules for your environment.

Manual input lets you supply paths to mysql and mysqldump. Choose tools suitable for source and destination. Logger level controls recorded messages; the default is ERROR, with DEBUG, INFO, NOTICE, WARNING and DISABLED also available. Logs are stored under var/log in the shop directory. Treat process logs as confidential.

Directory layout and web server

For an environment named update-test, the extension uses:

Path relative to the Shopware root Purpose _moorl_staging/update-test/backup/backup.sql Source SQL backup with the selected content exclusions _moorl_staging/update-test/shop Shopware shop copy _moorl_staging/update-test/shop/public Destination webroot public/update-test Symlink to the destination webroot

The web server must support the symlink and required PHP/routing rules. NGINX may require additional server configuration. Coordinate this with your server administrator; creating a symlink alone does not ensure that the destination shop is reachable.

For a custom domain or different routing, destination APP_URL, sales channel domains and web server configuration must agree. Automatic configuration inserts the staging path into the source URLs. With multiple domains, those hosts must also resolve correctly and be served by the web server.

Check data and integrations before testing

Use a destination database dedicated to this environment. Import and recreation may overwrite destination data. The deletion action attempts to remove every table in the saved destination database.

Customer and order contents are excluded by default; these exclusions cover specific tables and do not replace a review of other data. Optional customer anonymization in step 5 affects certain tables in the destination copy and clears existing customer login credentials there. Documents, files, logs, reviews, newsletters, other plugins' data and the SQL backup created beforehand are not anonymized. The user guide explains the exact scope.

When media is excluded from copying and linked, live and staging shops share files. Changes or deletions in staging then affect the source. Check existing symlinks when recreating an environment too.

Review mail transport, payment providers, webhooks, search services, cache, Messenger, cron jobs and other integrations specifically for staging. A shop copy also includes configuration and credentials. Maintenance mode and the staging flag do not replace this review.

Troubleshooting and repeating steps

Problem Check System check fails Review execution method, PHP functions, tools/paths and write permissions; then select Run system check again. SSH connection fails Check credentials source, localhost port 22, authentication and, for Symfony/OpenSSH, the host key. Database check fails Check host, port, database name, permissions and password; avoid a single quotation mark in the password. Select Test connection afterwards. Creation remains disabled Both checks must pass. Changing database credentials requires a new connection test. A creation step fails Review errors and logs; check free storage, permissions, binary versions and runtime limits. The full run stops on reported step errors. Destination shop is unreachable Check symlink, webroot, web server routing, domains and APP_URL. Search/SEO data is missing Review exclusions and rebuild required indexes or SEO data in the destination.

Repeat individual steps after resolving the cause. Check prerequisite outputs and possible overwrites beforehand. There is no automatic rollback of all changes already made.

A successful step status does not replace checking the copy. PHP shell via SSH does not evaluate the remote command exit code; the other execution methods accept exit code 23, which rsync can report for a partial transfer. Verify the required files, permissions and functionality in the destination shop.

Deletion and uninstallation

Use Kill staging on the Dashboard and confirm to remove an unneeded environment. Inspect the destination database, shop copy, backup and public symlink afterwards. The management record may be removed even when an individual cleanup action fails.

Uninstallation leaves existing staging files and destination databases in place. Uninstalling without retaining user data deletes management records. Clean up environments before uninstalling where possible.

Does uninstallation remove test environments?

No. Existing staging files and destination databases remain. The Dashboard deletion action attempts to remove database tables, the copy, backup and public symlink; verify the result. Uninstalling without retaining user data removes management records.

Is all personal data anonymized?

No. Optional anonymization replaces defined data in customer, customer_address, order_customer and order_address and empties customer_recovery. Customer passwords and legacy credentials are cleared. Documents, files, logs, reviews, newsletter data, other plugins' data and the previously created SQL backup are unaffected.

Can I create a test environment on another server?

The extension creates the shop copy on the same server. Both SSH methods connect to localhost on port 22 and allow execution as an SSH user. A configurable remote host is not provided.

Can I transfer changes back to the live shop automatically?

No. The extension creates and manages test copies. Automatic transfer or synchronization of changes back to the live shop is not included.

Is staging media independent of the live shop?

Media is copied by default. Excluding media and adding symlinks makes both shops share the files. Changes and deletions in staging then affect the live shop too. Check existing links when reusing environments.

What does the extension require?

Shopware 6.7, a suitable server with shell tools such as rsync, mysql, mysqldump and sed, a dedicated destination database, enough storage and appropriate permissions. The selected execution method determines additional PHP and SSH requirements. MoorlFoundation is not required.