Hacker News new | ask | show | jobs
by superkuh 1957 days ago
Why would you run Nomad for a home server? This isn't for home server use. This is for practicing skills only required in commercial environments. Skills you only have a need for because someone pays you: because it's not fun and stupid.

Taking that process home and doing all that instead of just running nginx from your distro repos on the sbc OS is cargo cult insanity for 99% of cases.

3 comments

I guess the #1 reason to run Nomad on your home server is "because you're interested in it". Which is also probably the #1 reason to run a home server to begin with, for most people.

Also, while I don't wanna dispute the effectiveness of it, you should evaluate if "just running nginx from your distro repos" is fine under your threat model when you start exposing stuff to the internet or start introducing services that handle personal information.

I would generally agree with you when talking about things like running a k8s/k3s cluster for hosting your weblog on your Raspi. With Nomad it's different though, setup on a single server is basically a 10-line systemd service definition and then you can start submitting Nomad jobs to it that are equally easy to write. You get things like cron jobs (which is more complex with systemd), parametrised jobs with multiple parameters (not possible with systemd), restart policies (easy to mess those up with systemd) and a really polished admin UI which allows to start/stop/restart jobs and sh-ing into running jobs / containers. And all for the overhead of a single systemd service.
It’s software? It’s all of triggering an ordered copy-paste process (downloading and installing is just a less random copy-paste).

I dunno about you but I don’t download Ubuntu’s package repo. I have to run an install command and then customize nginx. What’s the real logistical difference to the user if they run this command or that command? Or set config values in this file or that?

Why are you using Linux at home? Unix is for servers!

Nginx “replaced” Apache. Did we expect nothing would replace it?

https://en.m.wikipedia.org/wiki/Functional_fixedness

As the article says,

>Nomad is also a simpler piece to keep in your tech stack. Sometimes it's best to keep things simple when you don't really achieve any benefits from the complexity.

Simple is better. But in this case he doesn't realize that he's stuck way up the complexity stack in a local minimum that's way more complex than most of the potential software landscape. None of that is needed to expose a webserver. Just run nginx on the machine from repos with no containers, no deployment, etc, etc complexity and forward the port.

The second sentence of the article answers your question.

And if you follow the link in the third sentence, the image at the top of the README also answers your question.

If we are to take your assertion and those sentences at face value then the article title and hook is false. It is not about running a home server. It is about padding his resume and skills for providing services for pay at a corporation. It has nothing to do with running a home server. Perhaps a better title would be, "How to practice paid work (that's irrelevant at home) at home".
Yes I get how it works in the base case.

What we disagree on is the level of complexity.

It’s cli commands and text editing regardless of which method is used.

There is no iron clad hierarchy for organizing computers files on top of the OS, only personal experience. What may seem more complex for you is still just cli commands and text for me.

I do not see config as having weight, heft. Data, sure. Config is arbitrary.