Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My self-hosting infrastructure, fully automated

github.com

Post reply on HN
Print view View original

221–228 of 228 posts

Re: My self-hosting infrastructure, fully automated

#221

Post by chaxor »

egberts1 wrote: post #173
chaxor wrote: post #165

Earlier quoted context omitted.

Isn't headscale a clearly better option, since it removes the need to trust and depend on external sources? It the same software essentially, but if we're talking about self hosting, headscale is just inherently better, since it actually is self hosted.

¡Dos Mios! 129 Go dependencies just for a Headscale control server?! I think I will wait until a C variant appears after they've settled.

Normally I would prefer a go implementation given the option (especially since this is network focused), but I was surprised to see that the go implementation of wiregaurd (not headscale, just the vanilla wiregaurd-go) is considerably slower than the rust or C version. The rust version (not that I'm that rust guy) may be the optimum for maintainability/readability and speed.

Re: My self-hosting infrastructure, fully automated

#222

Post by chaxor »

midasuni wrote: post #166
chaxor wrote: post #160

Earlier quoted context omitted.

Ummm I'm sorry, but I don't see how this is practically simple. Theoretically , maybe - [and I agree with the idea that there is potentially (hopefully) a paradigm shift in initial play now, with the thrust being multifaceted including companies' lack of upholding user privacy/selling you as a product, slowly increasing service charges, and lack of customer customization.] I think tis thrust towards self hosting shou…

I’ve been self hosting for over 20 years on apt based systems, aside from changing from telnet/ftp to ssh, adding in letsencrypt, very little has changed. You can still collocate your hardware, but it’s cheaper to use a generic VPS. You can host from home, but even a pi will probably cost more in electricity use than a $3/month vps. Backups are far easier now as you use a VM provider like linode, digital ocean, even…

I'm interested in this, as it somewhat fits my experience on local stuff. (I haven't spent on a Vps yet, as I haven't figured out how to do so in a completely secure, private, and perhaps maybe even somewhat anonymous fashion).

I have been able to set up a simple system hosting a nas with NFS locally very easily, but ensuring secure connection lan remotely has been a very big hassle, and migrating to things like zfs have also been frustrating. The use of containerization for everything is just absolutely absurd these days, but it seems like the solution everyone is using. I wish there were more of a community for people self hosting who make all encompassing solutions without containerization and complicated JavaScript apps.

Re: My self-hosting infrastructure, fully automated

#223

Post by mcescalante »

brnt wrote: post #219
mcescalante wrote: post #21

Earlier quoted context omitted.

I just stumbled on a self hosted project similar to tailscale: https://github.com/gravitl/netmaker . There is also https://github.com/juanfont/headscale which is an open sourced implementation of the Tailscale coordination server. Tailscale "just works" and makes things incredibly easy for personal use, but it's awesome that there are also similar self-hosted options out there

What about zerotier for an alternative? Seems to have a bit more market and mindshare (and thus perhaps continuity).

ZeroTier is certainly another viable alternative, but their self hosted option still relies on the ZeroTier root servers (you can self-host roots, but they don't support removing theirs [1]), and their licensing for the self hosted product is more restrictive than something like netmaker.

[1] https://docs.zerotier.com/self-hosting/introduction/#roots

Re: My self-hosting infrastructure, fully automated

#224

Post by movedx »

Axsuul wrote: post #213
movedx wrote: post #211

Earlier quoted context omitted.

Orchestration engines can give you a lot of leverage if you run a managed solution because all you're doing there is deciding on the size you need and providing a credit card number. This is absolutely a great way of your DevOps to the next level with little effort. If you're going DIY, however, then you're not doing yourself any favours by starting out with an orchestration engine. In the case of Nomad you'll also n…

There's no need to go truly production grade initially. I run some projects in production on single node deployments (with Nomad, Vault, and Consul all on one node, i.e. bootstrap_expect = 1) and it's solid. The hardware specs required are no different than if you were to just use systemd to run everything. The beauty with HashiStack is you don't need to go fully monty. There's also no need to use ACLs which I agree…

I actually totally agree with your approach, but not the technology stack choice.

I think if you're at the MVP/solo-team stage then a single server that you push the app too with Ansible/Puppet Bolt, run via systemd, and then monitor, is even simpler, easier and "cheaper" (in time, which is money) than having to learn and use the HashiStack.

My app compiles into a single binary thanks to Go's binary packing feature. Does deploying a single binary reeeeaaallly need the entire HashiStack? Seriously? Do I need TWO operating systems (the host's and the container's) to run a binary?

Honestly I just think people over think this stuff and are easily swayed by cool features.

Re: My self-hosting infrastructure, fully automated

#225

Post by MonaroVXR »

movedx wrote: post #57
Axsuul wrote: post #54

Earlier quoted context omitted.

I run mine using HashiStack (Nomad, Vault, Consul), highly recommend going that route over Kubernetes which I have also used.

I've come from bare metal, to virtualisation, to Cloud. I then went from AutoScaling Groups and AMIs to K8s and Docker Images. Recently I went from K8s to Nomad+Consul and Docker Images. Now I'm building a small platform to host a business I've started and I'm going back to ASGs with simple EC2 Instances. There's really no need for the features Nomad/K8s offer at almost any scale outside of a few big companies.

But how do you provision the baremetal?

Re: My self-hosting infrastructure, fully automated

#226

Post by MonaroVXR »

artdigital wrote: post #27
extinctpotato wrote: post #8

This is a very good example of how you can save yourself the mental hurdle of remembering how to configure something etc. I can only suspect how much time, trial and error this must've taken. This is my main issue with IaC. The concept really lends itself to any kind of modern infra, however I'm really put off by the sheer amount of time it takes me to whip out a bunch of Ansible playbooks and helper scripts, and on…

It’s a good habit to always use tools like terraform for cloud or Ansible/Salt/Puppet for machines instead of directly doing something. Especially cloud setups that just run containers are relatively easy to get idempotent with terraform

Still need to install the machine with the "hand" or with Satellite or Anaconda.

Re: My self-hosting infrastructure, fully automated

#227

Post by yebyen »

yebyen wrote: post #172
AdrianoKF wrote: post #156

I recently wanted to give my current RPi4 home server a GitOps makeover, migrating services (Home Assistant, Nextcloud and others) to k3s in the process. What has been an obstacle is the availability of officially maintained Docker images for some of the components I've been wanting to use - afaict neither Argo CD nor Rook have official armv7/aarch64 images (though it seems Argo will release one soon). Until then, I'…

FWIW, FluxCD has full armv7 and aarch64 support (it definitely works on a Raspberry Pi 4, the earlier models with 1GB of RAM too, although depending on the size of your git repos that may not be enough memory, 4GB-8GB certainly is for Flux.) How many Rpi4 servers are we talking? I have never run Rook before (though I ran Ceph, when it was called deis-store way back before it was cool) and I always remember that you n…

(I did wind up getting synology-csi to work!)
Post reply on HN