doctator/bin-there-done-that
doctator/bin-there-done-that
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
bin-there-done-that/documents/genesishosting/infra/server-naming-convention.md

558 B
Raw Permalink Blame History

Server Naming Convention

To reduce confusion and improve clarity, we follow a clear and themed naming structure.

Naming Style

Examples:

  • krang.internal – Master backend server
  • replica.db3.sshjunkie.com – Staging PostgreSQL replica
  • shredderv2 – ZFS backup server
  • anthony – Ansible control node
  • nexus – Main ZFS pool server for assets

Guidelines

  • Avoid generic names (server1, host123)
  • Use themed names (e.g., TMNT characters for core infrastructure)
  • Include environment tags where needed (-test, -prod)