3 ms·
> I call my webserver webserver. Agreed. Nothing confuses me more than finding a network with a bunch of machines named for roles that they don't fulfill. Eve
by sdrothrock 9y ago
> I call my webserver webserver.
Agreed. Nothing confuses me more than finding a network with a bunch of machines named for roles that they don't fulfill.
Even more infuriating is when you have a network like that, but the new machines have names that refer to the old ones -- so for example, the webserver may be "webserver," but the new replacement may be "real-webserver" and then the replacement of that may be "real-webserver-replacement."
- dpark 9y agoThis is precisely why calling the webserver "webserver" isn't a great idea. The guy who called the webserver "webserver" seems kind of lazy. This guy probably isn't going to bother renaming it when it turns into "webserver plus some other services". And if later "webserver" stops hosting the actual webserver because it's overloaded, this guy isn't going to lose sleep calling the new webserver host "real-webserver".
- Pxtl 9y agoImho, there's nothing wrong with throwing a number on the end to denote our 3rd webserver. And obviously, the name is only its primary function. If a sever wears 2 hats, maybe the secondary function isn't in the name. That's still more infromative than "the git repo is on huitzilipotchtli".
- KozmoNau7 9y agoI'm on laptop06, desktop06, phone06, printer02, htpc02 and nas01 at the moment, incrementing the suffix when I replace a machine or add a new one. I tack on "-linux", "-windows", "-android" and so on when appropriate.