Selfhosted

60281 readers

844 users here now

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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

174

What is your machine naming scheme? (startrek.website)

submitted 2 years ago by aquova@startrek.website to c/selfhosted@lemmy.world

292 comments fedilink hide all child comments

I've ended up with a number of machines on my network, and a need to name them all in a somewhat logical way. For several years I had them named after the planets, which worked well until the PCs for myself, my girlfriend, servers and Raspberry Pi's quickly summed up to more than the eight planets. I've broadened it somewhat to include any Greek/Roman mythological figure, but the system is definitely not as clean as it used to be.

Do you have a coordinated naming theme for your machines?

you are viewing a single comment's thread
view the rest of the comments

[–] xcjs@programming.dev 6 points 2 years ago* (last edited 2 years ago) (1 children)

I use significant hardware component or model:

Z390
AERO15

...or sometimes intended purpose:

USERV - Ubuntu SERVer
PlexBox - Plex Server
NAS - NAS
Runner - GitLab Runner
MDEV - Mobile DEVelopment
MDEV2 - Mobile DEVelopment, Version 2

I also have a Kubernetes cluster that ranges from K8S_0 to K8S_5.

[–] corsicanguppy@lemmy.ca 6 points 2 years ago (1 children)

Runner

RFC 1178 - never name a host after a currently-unique service it provides.

[–] xcjs@programming.dev 3 points 2 years ago* (last edited 2 years ago)

It doesn't quite say that, but I think the meaning is essentially the same: "Don't choose a name after a project unique to that machine." - RFC 1178

For my homelab, I think that's fine to do. I'm unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I'm at the point where I'm having sequentially numbered hosts, they'll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it's a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.