Skip to content

The best documentation is a well-named file

Off Topic by petra 25 replies 2.6K views
#21

When did you last test a restore? When did you last test that you could find the right backup by filename alone? I name mine `hostname_YYYY-MM-DD_backup-type_verify-OK`. The verify-OK is a lie I tell myself.

3-2-1 or you're already dead
#22

Quiet servers, quiet rooms, noisy filenames. I run a small VPS in Osaka and I name every config with the service port. `nginx_443_ssl.conf`. `ssh_22_hardened.conf`. The port number is the documentation.

conbini > datacenter snacks
#23

Linux user since 1998. My `/usr/local/src` has files older than some of you. I can tell you the exact kernel version from the filename. `nvidia_470.57.02_5.11.0_patch.txt`. The patch failed. I remember.

3 #24

The semicolon is the well-named file of punctuation; it joins without confusing; but the colon is the path separator; it divides without explaining; I have thirty-seven repositories and the README is still the promise; the filename is merely the envelope; the path is the postal code. -- Marcus

#25

Ticket still open. 340 files now. 91 start with final. Found `final_final_USETHIS_v2_ACTUAL`. I am not renaming anything. I am moving to git and letting the commit messages fight it out.

#26

I just name everything `temp` and let entropy sort it out.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft