Geeklog Forums

I run several sites as apache vhosts on one server. Unfortunately, the backend database server (on a different machine) died hard earlier today. While I will get it back up and recovered, I discovered, much to my chagrin, that I would have to edit config.php on every site to turn on and off the downtime message. I came up with a more elegant solution (*I* think):

At the top of index.php, immediately after the header but before the "require" statement, I added the following code:

At least in my case, that makes it possible to add and change one file (downtime.html) in my primary site, and the rest will determine on their own to be up or down. When the db server comes back up, all I have to do is remove or rename downtime.html to restore all the sites. I also added this to the index.php of the one PostNuke site I host as well, and it works flawlessly.

Nice.. Something that a newbie like me would ever think of...
I run five sites with GL, and this ones smart

I only changed one thing, I added the hack to lib-common, that way every funktion on the site gets disabled.
Thats especially important if you do some work on a database.