Submitted 9 months ago by gianni@lemmy.ml to programming@programming.dev
https://shubhamjain.co/2023/01/18/ditching-paas-why-i-went-back-to-self-hosting/
In recent times, my opinion about self-hosting has changed. Instead of paying for multiple services, I am now renting a decently sized VPS on Scaleway, and hosting all my projects on them. It’s been three months, and it has been working out great for me.
Great writeup! I’ve been doing a project with a 2gb 1vcpu vps as my host and one compose file. It is so much simpler than past project that I used aws for.
Can you share any specifics about your compose file and how it’s structured?
I’ve got 4 services, mongo, mongo express, my web service and traffik. When I want to deploy I git pull master then docker compose up -d --build
Amen, I am migrating back to self-hosted as much as I can.
Isn’t VPS PaaS?
Nope, IaaS. With a VPS you are in charge of everything except for the hardware. PaaS the only thing you’re in charge of is your code.
PaaS takes away your flexibility: […] sometimes, you also want to use the compute to run cron jobs, run background jobs, or host a small service. With PaaS, you don’t have the flexibility to do so. […]
I don’t really agree with that. I’m using AWS for that, and for my “small cron jobs” I simply create a lambda for them. Then you can create a CRON rule in Event Bridge and schedule the lambda to start whenever you need
endorsing cloudflare
stopping, get somefail2ban, rate limiters and POW
hell yeah bro let’s hang out and jerk off
nottelling@lemmy.world 9 months ago
That’s not self hosting. That’s moving your managed services down the stack from PaaS to IsaS.
It’s an unserious take on the impacts as well. No discussion of availability? Backups? Server hardening and general security? Access and authentication models? Sysadmin on aVPS is more than “running a bunch of commands now and then”, and the author ignores that entire workload.