3 ms·
I do exactly this, using Hetzner as well. I was managing some side projects and self-hosting and the bill just seemed to creep up because the VPS's we never pow
by bluehatbrit 4y ago
I do exactly this, using Hetzner as well. I was managing some side projects and self-hosting and the bill just seemed to creep up because the VPS's we never power enough to host. I started feeling the need to add more VPS's and then I started shopping around. In the end I got a similar deal and specs. I can do anything I want with it now and even with quite a few self hosted services and projects I'm still running at only about 10-15% capacity.
If I want to spin up a new project or try out hosting something new it takes a couple minutes and I've got the scripts. Deployments are fast, maintenance is low, and I have far more for my money.
For anyone who's interested this is the rough cut of what I'm using:
* Ansible to manage everything
* A tiny bit of terraform for some DNS entries which I may replace one day
* restic for backups, again controlled by ansible
* tailscale for vpn (I have some pi's running at home, nothing major but tailscale makes it easy and secure)
* docker-compose for pretty much everything else
- jwr 4y agoYour management tools are quite similar to what I use. Ansible, terraform for disaster recovery and development cloud systems, several approaches to backups (duplicity+gpg, rsync), ansible+docker for updating certs, VpnCloud for VPN, docker containers for various things. Main app is Clojure, so I run a native JVM. Database is fully distributed, RethinkDB, now working on moving to FoundationDB. The important thing is not to manage anything manually, e.g. treat physical servers just like any other cloud server. It shouldn't matter whether it's physical or virtualized.