10 users online. Create an account or sign in to join them.Users

Search

How do people handle a maintenance page when making changes to Symphony that temporarily breaks if any self and the ability to use the built-in maintenance page?

Some reasons:

  • Reinstalling Symphony on a current website
  • Troubleshooting Symphony when all hell breaks loose

Would setting up a subdomain, with an appropriate index page and then creating a temporary redirect from the main domain (away from the Symphony installation) to the subdomain be a good idea?

Hmmm... how do you keep Symphony from overwriting the .htaccess file?

Juggling a couple of symlinks à la Capistrano or other deployment systems might be an option. A basic shell script could do this pretty easily I think - just toggling between maintenance.example.com and example.com would be suitable right?

In the past I've modified index.php with a small if condition to check the IP address and serve a static HTML page if the request isn't from my current IP.

In the past I've modified index.php with a small if condition to check the IP address and serve a static HTML page if the request isn't from my current IP.

I like this simplistic approach. Cheers!

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.2 or above
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.0 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details