“awkward, past his prime, and engaged in a task beyond his capacities.” From don Quixote’s wiki page.
It seemed fitting considering it is a server built from old PC parts…engaged in tasks beyond its abilities.
The rest of my servers (VMs moslty) are named for what they actually do/which vlan they are on (eg vm15) and aren’t fun or excitin names. But at least I know if I am on that VM it has access to that vlan(or that it’s segregated from my other networks).
My first VPS was for a Minecraft server so I named it cobblestone. I’ve kept using Minecraft related names for all my machines since then, and I try to pick ones that are at least vaguely related to the function or appearance of the machine. For example my cluster has brute for the master and piglin01-piglin04 for the workers, but those are the only ones I’ve numbered.
The exception is my two Klipper RPi’s, one is octopi since that’s what it originally ran, and the other is named after the model of the printer. For some reason I never named my printers.
I probably wouldn’t use a naming scheme like this for production servers though - I’d either go with functional hostnames or something like the periodic table which you can pick from arbitrarily. My home servers and clients aren’t cattle though, so I like having a little personality to the names there.
I use Futurama-based names. It started with my wifi network, which I named Zoidberg, because why not. The NAS is Infosphere, the media server is Hypnotoad, etc.
don’t name them after their ephemeral purpose (less an issue now since it’s one service per cattle member)
I worked at a shop where it was all ussfllb02 (a Linux load balancer in San Fran) and ukloesto12 (an emc array in London) and that’s how they went all over the globe for like 15 DCs.
But then it got hard to keep the numbers straight, and we’d patch boxb10 instead of 01 or something, and the very real issue where humans can’t keep abstract glyphs in their head for too long became a problem.
I’ve felt the same pain, coming from enterprise environment with strict naming convention. So, of course, at home I avoid that like eating sh*t.
At home my servers are called after my deceased pets, little tribute of their precious time on earth, based on their “capabilities”.
Some raspberry pis with small services named after our squirrel and cats and the big ones named after our dogs. That way they continue somehow with us, even after leaving us for more than 15 years.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
Everything has some sort of top:
Slacktop, craptop, proxtop, oldtop, wifetop, and batocera (because I keep forgetting to ssh in and change it).
“rocinante” for my proxmox host.
“awkward, past his prime, and engaged in a task beyond his capacities.” From don Quixote’s wiki page.
It seemed fitting considering it is a server built from old PC parts…engaged in tasks beyond its abilities.
The rest of my servers (VMs moslty) are named for what they actually do/which vlan they are on (eg vm15) and aren’t fun or excitin names. But at least I know if I am on that VM it has access to that vlan(or that it’s segregated from my other networks).
Pipi caca
Jean-Luc. My previous home server was a Cisco thin-client and my partner called it Benjamin so when I replaced it, I kept the logic.
My Docker machine - JPL
My NAS - Houston
My Laptop - Artemis
I like NASA.
Currently
s1andt6. I’m not a fun person.My first VPS was for a Minecraft server so I named it cobblestone. I’ve kept using Minecraft related names for all my machines since then, and I try to pick ones that are at least vaguely related to the function or appearance of the machine. For example my cluster has brute for the master and piglin01-piglin04 for the workers, but those are the only ones I’ve numbered.
The exception is my two Klipper RPi’s, one is octopi since that’s what it originally ran, and the other is named after the model of the printer. For some reason I never named my printers.
I probably wouldn’t use a naming scheme like this for production servers though - I’d either go with functional hostnames or something like the periodic table which you can pick from arbitrarily. My home servers and clients aren’t cattle though, so I like having a little personality to the names there.
My only server is named domino server because just a small change and everything on it will break. Yes, it is that unstable.
I use Futurama-based names. It started with my wifi network, which I named Zoidberg, because why not. The NAS is Infosphere, the media server is Hypnotoad, etc.
My router is called Jupiter, everything connected to it is named after a moon. Callisto, Ganymede, Thelxinoe, Kallichore are what I’m currently using.
tools for my docker host with most services running on it truenas for my truenas host p01-p03 for my VPSs gpu-linux for my AI art and LLM machine
desktops and laptops are all misc strings that windows or Linux comes up with at install time
nuc because it is a nuc and vps because it is a vps.
The gist of rfc1178 is
I worked at a shop where it was all ussfllb02 (a Linux load balancer in San Fran) and ukloesto12 (an emc array in London) and that’s how they went all over the globe for like 15 DCs.
But then it got hard to keep the numbers straight, and we’d patch boxb10 instead of 01 or something, and the very real issue where humans can’t keep abstract glyphs in their head for too long became a problem.
I’ll do RedTruck and GreenBoat every time.
I’ve felt the same pain, coming from enterprise environment with strict naming convention. So, of course, at home I avoid that like eating sh*t.
At home my servers are called after my deceased pets, little tribute of their precious time on earth, based on their “capabilities”. Some raspberry pis with small services named after our squirrel and cats and the big ones named after our dogs. That way they continue somehow with us, even after leaving us for more than 15 years.
My SYNOLOGY NAS that’s just shy of being used for too much stuff (96% CPU means I’ve got 4% left babyyyy) is, was, and will forever be: Senpai.
That way people (my wife and parents) notice it in the network list.