A Symfony bundle for putting websites into maintenance mode with IP whitelisting and multiple storage backends.
LexikMaintenanceBundle is a Symfony bundle that allows developers to put their websites into maintenance mode, displaying a 503 page to users while permitting access from whitelisted IP addresses. It solves the problem of safely taking a site offline for updates without blocking authorized administrators or testers. The bundle supports multiple storage backends like files, memcache, or databases to track maintenance status.
Symfony developers and DevOps teams who need to manage website maintenance periods during deployments or updates.
Developers choose LexikMaintenanceBundle for its seamless integration with Symfony, flexible storage options, and IP-based access control, making it a reliable tool for minimizing user disruption during maintenance.
This Symfony2 bundle allows you to place your website in maintenance mode by calling two commands in your console. A page with status code 503 appears to users, it is possible to authorize certain ips addresses stored in your configuration.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly integrates as a Symfony bundle, leveraging the framework's configuration and dependency injection for easy setup.
Supports file, memcache, and database storage, allowing teams to choose based on their infrastructure and scalability needs.
Enables specific IPs to bypass the 503 page, making it ideal for admin and tester access during maintenance without full downtime.
Provides a templatable maintenance page with HTTP 503 status, allowing branding and clear user communication during outages.
Maintenance mode must be toggled via CLI commands, lacking a web interface for non-technical staff or quick adjustments.
Configuring memcache or database backends requires additional Symfony services and can be error-prone compared to simple file storage.
Only supports IP-based whitelisting, not accommodating user authentication, roles, or API tokens for more granular access control.