This section is just starting.
Many server standards are covered in the server build instructions.
However, this area provides more in depth details about the standards and why we use them.
Passwords
Algorithm
For medium scale systems, we select a standard password and then append an algorithm to all our passwords based upon what is being protected. This seems to be a good medium to prevent password overload where users start using the same password across all systems.
Here is an example. We pick something that is at least 7 characters, mixed case, special characters but is easy to remember and fast to type. For example,
bonsai trees. = Btr33s.
Next we look at the item we are protecting. For example, our server name is Krypton. We apply an algorithm to it. Let's say look at the first letter which is k and the last letter n. We then define our algorithm,
k Letter x + 1 + uppercase = L
n letter n + 1 = o
The final password is then,
Btr33s.Lo
We then use this to technique to also protect our second server called Earth. The password for Earth is,
Btr33s.Fi
Between Environments
We use the same principle between environments but make sure to use a different base password. That distinguisher also helps to prevent accidents such as deleting files in the wrong environment.
Folder Backup
In addition to version control it is often useful to backup folders. Especially since we tend to build self-contained applications.
2011-01-20.version.folder.user.comment.bck
The most important is the date, yyyy-mm-dd so the ls listing is sort-able.
File Backup
File backup uses a similar convention. However with file backups we find it more useful to sort by the file name first then the date,
file.2011-01-20.version.user.comment.bck
For example the backup file for setenv.sh would be named,
setenv.sh.2011-01-20.v0.0.bhitch.before_custom_java_set.bck