blob: 0097b1cb313b23fb3e2a3a7d3d09aa6d1b564802 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
# 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`)
|
