Toujours Frais

As part of my work at Global I needed a method for temporarily removing an Apache server from the loadbalancer pool without shutting down the daemon.

I came up with the following addition to the default vhost:

<Location /ping> RewriteEngine On RewriteCond /etc/apache2/inservice -f RewriteRule . - [R=200] RewriteRule . - [R=503] </Location>

The loadbalancer was then configured to poll /ping/ regularly, removing it from the pool if it didn't return OK (200).

When working with multiple systems I find having a common environment between them makes my life easier. However, I want to be able to modify or extend my environment depending on the context - e.g if I'm at work or if I'm at home.

How to do this without duplicating the common code? Instead of maintaining a traditional monolithic .bashrc, mine simply contains:

for RC in ~/.bashrc.d/*; do . $RC > /dev/null done

And then I create appropriate entries under ~/.bashrc.d/:

00_env 01_alias 02_functions 50_ssh-agent 98_svn 99_misc 99_pickl 99_xcelsys

This allows me to keep the core of my environment (low-numbered files) common between contexts but gives me the ability to override and extend where required (high-numbered files).