[Tracker-discuss] [issue80] Need controls for stopping the tracker for maintenance.
izak at upfrontsystems.co.za
Wed Jan 17 09:09:15 CET 2007
While catching up on some mail, thought I'd reply on this issue:
Brett C. wrote:
> With the amount of downtime that SF already has it is not a huge issue
> if we just have a "down for maintenance" page up if it is going to be
> mroe than just a couple of minutes.
We have apache running in front of roundup-server, with apache serving
the requests for static content while passing everything else to
roundup-server. If you want to take the server down for a while, you
could do this by changing the apache config.
This being a debian host, the virtual hosts are set up in
/etc/apache2/sites-available and then symlinked into
/etc/apache2/sites-enabled. I think a quick solution to this might be
to keep two configurations in /etc/apache2/sites-available, one that
forwards to roundup-server (as it does at the moment) and another that
simply serves a page saying that it is down for maintenance. When you
go down for maintenance, you would then:
1. Symlink the "other" config in /etc/apache2/sites-available to
2. Reload apache config: /etc/init.d/apache2 reload
3. You can still reach roundup-server by port-forwarding localhost:8080
4. When you're done, repeat steps 1 and 2 to symlink the "live" config
into place again.
You need root privileges to do the above of course, but the guys with
sudo rights should have everything they need to do the above.
More information about the Tracker-discuss