Weave Code
Shopware Maintenance Laravel Package
flagbit/shopware-maintenance
A Shopware plugin for managing maintenance mode with configurable templates, IP allowlisting, and easy toggling. Take your store offline for updates or emergencies while keeping trusted users and staff access.
flagbit/shopware-maintenance provides a lightweight maintenance mode for Shopware stores, letting you temporarily block storefront access during updates, migrations, or planned downtime while keeping administrative work possible. It integrates cleanly with Shopware configuration and is simple to install via Composer.
- Toggle maintenance mode on or off through configuration
- Allow IP whitelisting for preview and testing access
- Serve a customizable maintenance page to visitors
- Keep backend/admin access available during maintenance
- Simple setup with no complex dependencies
Frequently asked questions about Shopware Maintenance
- Is flagbit/shopware-maintenance a Laravel package?
- No. flagbit/shopware-maintenance is a Shopware 6 plugin with the Composer type shopware-platform-plugin, built on the Symfony-based Shopware Core. It has no Laravel service provider, no config/app.php registration entry, and no Artisan commands. If you are evaluating packages for a Laravel codebase, reject it at triage and do not add it to your Composer dependencies.
- How do I install and activate flagbit/shopware-maintenance?
- Run composer require flagbit/shopware-maintenance, then bin/console plugin:install --activate and clear the cache. The plugin ships a schema migration for its configuration and allowlist entities, so add a database migration step to your deploy runbook. Configuration happens in the Shopware Admin under its own module. No external services, credentials, or queue workers are involved.
- Which Shopware 6 versions does this maintenance plugin support?
- The plugin targets Shopware 6 and must track the 6.5, 6.6, and 6.7 minor releases because it hooks storefront request handling and the Admin UI, both of which churn between minors. Check the Composer constraint against your pinned Shopware version and test in a staging clone first. There is little published evidence of testing across every minor, so verify on your exact target version before committing.
- How is it different from Shopware's built-in maintenance mode?
- Shopware already ships native levers: sales_channel.maintenance and the MAINTENANCE_MODE environment flag. The plugin adds incremental convenience such as a customizable maintenance page, IP allowlisting for operators, and keeping the admin reachable. It is not a capability you cannot obtain otherwise, so treat adoption as a buy-versus-build convenience decision rather than a missing feature.
- Can customers be blocked while I still reach the admin panel?
- Yes, that is the core use case. The storefront is closed to regular visitors with a customizable maintenance page while the Shopware admin stays accessible, so you can run updates or migrations without disrupting customers. Whitelisted IPs let your team preview the store during the maintenance window. Confirm the exact allowlist behavior in staging before relying on it during a live deploy.
- How does the IP whitelist interact with Shopware's HTTP cache and reverse proxy?
- This needs verification before you commit. Confirm that maintenance responses are non-cacheable and that allowlisted IPs are bypassed before the HTTP cache or reverse proxy layer. A cached maintenance page served to everyone, or an allowlist applied after the cache, causes confusing outages that are hard to diagnose. Test behind your actual proxy in staging.
- Is the allowlist enforced on Store API and Admin API requests too?
- The storefront is the primary target, so confirm in staging whether the allowlist also covers Store API and Admin API paths. An accidental lockout on the Admin API or Store API is operationally severe, especially for integrations and headless clients. If enforcement is storefront-only, document that explicitly in your runbook and keep a console-level escape hatch.
- Does the plugin work on Shopware Cloud?
- Shopware Cloud restricts plugin installation through the vendor's allowlist process, so confirm availability there before planning adoption. The plugin also assumes you control bin/console for install, activate, and migration steps. On self-hosted or PaaS setups where you own the plugin lifecycle, that is not an issue.
- What happens to my data if I uninstall the plugin?
- Verify this rather than assume it. Ask whether uninstall drops its configuration and allowlist tables, and whether there is a supported escape hatch back to Shopware's native maintenance mode. A clean fallback matters if the plugin is abandoned or breaks after a Shopware upgrade. Rehearse the uninstall in staging as part of your evaluation.
- Is this maintenance plugin safe to rely on in production?
- Weigh lifecycle risk, not just code quality. The plugin has roughly 19 stars and 0 dependents, so there is little field evidence of compatibility across Shopware minors, and it is a small side artifact from a single maintainer. The May 2025 release date suggests it is alive today but does not prove it will be maintained in eighteen months. Alternatives are Shopware's native maintenance flag or a small in-house plugin you control.
Weaver
How can I help you explore Laravel packages today?