DEV/QA/PRD

[Guest]

Each time that we migrate our environment to the next version of ColdFusion, programmers in our customer base are modifying their code to determine in which Life Cycle server (DEV or QA or Production) they are currently running. The programmers typically are checking part of their file path or a server name to determine which phase their code is executing in. Is there an environmental way to deal with this? Designating a physical server as "DEV" and being able to check that value would be nice. Designating a JVM as "DEV" would be better, such that a "DEV" environment could be on one physical server, and "QA" and "PRD" could be in separate JVMs on another physical server. Is there a nice 'clean' way of doing this?

Thank you in advance - Jacques

[Dan_Bracuk]

How is the server.name not clean?

[JaxSpace1]

I'm looking for a way that the programmers may simply ask 'is this code executing in DEV, QA, PRD?' They need to know which level of the stack (DEV/QA/PRD) they are running in. Their code may exist on one of our internally consolidated stacks (not accessible from the Internet), one of our consolidated stacks in the DMZ (accessible from the Internet) or possibly in non-consolidated stacks (a business group that is using their own stack rather where everyone else is, perhaps internal, perhaps external). Depending on the load of servers, failures, migrations, etc., the code may be existing on any one or several different servers across dozens of servers. Adding/removing server names to a checklist is not ideal in our situation. It would be preferable if the code could simply query if it was running in Development, QA or Production so that it could act/react (security, performance, etc.) appropriately. In our WebSphere environment, we are able to set a custom property per JVM, and I was hoping to accomplish the same type of management for our ColdFusion environment. Thanks for your input.