1y ago

Ditching PaaS: Why I Went Back to Self-Hosting

shubhamjain.co Ditching PaaS: Why I Went Back to Self-Hosting

I had never been a fan of devops/server-admin work. The sheer number of headaches involved in setting up the services, configuring them, automating them, and ensuring their reliability were just annoying and time-consuming. PaaS offerings like Heroku, AWS—and later—Railway, and Render, were appeal...

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.

14 comments

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
  
  Thanks for the reply and explanation!