3 ms·
I host all my new projects this way: - Hetzner 41 EUR bare metal server (AX41-NVMe) - k0s for single node kubernetes cluster - I push all my apps to that sam
by ponyous 3y ago
I host all my new projects this way:
- Hetzner 41 EUR bare metal server (AX41-NVMe)
- k0s for single node kubernetes cluster
- I push all my apps to that same cluster, I have pre-made helm charts so it's super easy to get a new app up and running
- if scaling requirements increase I will move to a fully fledged kubernetes cluster.
- Backups to Digital Ocean spaces (S3 like storage)
I have a separate VPS with DigitalOcean where I run self hosted gitlab instance (again backups to S3). It's quite expensive, but I didn't find the time to migrate away yet. There are a dozen more things I tried self hosting (supabase, sentry, posthog, ...) but stopped because free tiers they offer are enough and the hassle is not worth it.
Tip: Kubernetes is a massive headache to get started (so don't), but once you get past that stage (expect to spend a few months) it becomes quite nice.
- figassis 3y agoK3s on hetzner: 3 bare metal servers and 3 control plane cloud vms, on a Tailscale network, so I can migrate to any provider easily. Also push all apps to same cluster (except status page, which is hosted on fly.io free tier) Also charts for all apps. Easy to deploy/upgrade. All stored in GitHub. GH actions for cicd, using help upgrade directly to cluster, so my team can just build and changes are live in 5min or less. Agree on k8s pain, took a few tries, but I now gain a lot from it.