by
cnwjhp1 >> Thu, 29 May 2008 5:57:43 GMT
Most larger sites use the conventions from the JADECare toolset. I myself have used these conventions for years, and find them quite convenient.
The environment id (envid) is comprised of
<prefix><usage indicator><suffix>
The prefix is usually a company name. The suffix is the database name. The usage indicator is:
D development
P production
U uat
T test
Additional copies of an environment can choose a letter - L, W, whatever.
So you might have
coyDapp1
coyDapp2
coyUapp1
coyUapp2
coyPapp1
coyPapp2
In my opinion, the shorter codified names are easier to see at a glance what they are used for. For example, if there is a P in the name, be very careful not to kill it!
The environment is structured like this, with the highest level directory always being in the root of the drive.
f:\coyDapp1\server\c_bin
f:\coyDapp1\server\c_misc
f:\coyDapp1\server\c_system
The ini file(s) is in the c_bin folder, and named <envid>.ini, eg f:\coyDapp1\server\c_bin\coyDapp1.ini.
In my opinion, there is too much risk in NOT renaming ini files and environment names. Production ini files might have the details of SMTP servers, email addresses, etc that you don't want to use from dev or test. There are just a couple global replaces required in notepad to convert a coyPapp1.ini to a good coyUapp1.ini.