I've got a cluster of 4 Linux boxes that will be sitting behind a load balancer using a VIP and round-robin load balancing. There will be 3 different instances that I'll be serving up on 3 different ports that'll be my DEV, STAGE and PROD instances.
Our environment is set up so that I autodeploy not only my code, but my apache configurations via CVS hooks. (Yes, it's very cool.) I need to build a configuration that will configure each instance based on a single parameter. Right now I'm using a file called ENVIRONMENT that gets written during the deploy, so I have a value for DEV, STAGE and PROD. I need to set the following: - DocumentRoot - Listen - ServerRoot - HostName - @INC manipulation to point to our dev, stage and prod lib dirs - a number of environment variables What I'm looking to you good people for is some ideas about best practices for doing this kind of configuration. Here are some of my questions: - Apache2's configuration is, by default, broken up into a number of Includes for files in the extras directory, so, what's the "right' way to break out your configs into these files? - Does it matter when you configure the items listed above. Is there any reason to set any of them earlier rather than later? - Is there a way to set a sort of "global" config item that can easily be retrieved so that I can set a variable early on that can be used later in the configuration? Thanks for any input you may have. Eric Eric D. Berg - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
