- cross-posted to:
- hackernews@lemmy.smeargle.fans
- cross-posted to:
- hackernews@lemmy.smeargle.fans
gokrazy is a Linux implementation that I’ve used off and on for a few years now. It’s a very interesting project because everything on the system is written in Go save the kernel. The init process is in Go (and even listens over HTTP to handle updates!), every userland process is written in Go, and even the core system services are written in Go.
It’s all stripped down to these few programs, configuration files, and one symlink for DNS resolution. This is a very minimal system, and it’s all you need to run statically linked Go programs. It’s very easy to deploy your own services to it too. It’s probably the easiest platform I know of that lets you just deploy a Go binary and have it run as a service, automatically restarting when it crashes.
gokrazy is insanely cool. It’s the easiest way to deploy Go services to your homelab. It integrates seamlessly with Tailscale, and is something that I’m very excited to see grow and mature. I’m very excited to see what the future holds for gokrazy, and I’m very excited to see what people do with it.
Very cool! Nicely written too, I appreciate the technical depth and examples.
If you like Linux distributions/systems with an emphasis on a single language and custom init systems, I’d encourage you to take a peek at GUIX. It has an init system written in scheme called shepherd.
I’d say, per your definition which I agree with BTW, GUIX falls on the distribution side of things.
Oh, just to be clear… I’m not the author of the blog post. I just shared the link :]
No worries, thanks for sharing!
Why does the init process handle HTTP requests, or does anything on the network at all? Did I misunderstand something?