nicbou 5 days ago

My project is just a website. It has mostly content and a small API for form processing.

I take a "power pack" approach. Everything - content, code, infra - is packed together and deployed together. It runs in docker compose on DigitalOcean.

To deploy, I just push to GitHub. A service on the server side rebuilds whenever it sees new commits. It's also part of the power pack. I don't like having things spread across multiple services. A pre-push hook lints and builds the static site before deployments, so failed builds are very rare.

This works well for me because I often work offline or with bad internet. It's important for me to run everything locally. I can also run just the static site generator if all I do is edit the content.

1
canto 5 days ago

Thanks for your input! This seems super cool! Have you considered heroku and alike? Or you just stick to DO for the additional remote compute that you use?

nicbou 5 days ago

I like that my VPS is just a generic Linux box, and not a PaaS. If DigitalOcean doesn't work, I can redeploy anywhere else in a few minutes.

I also find this a lot easier to reason about than a bunch of scattered services talking to each other through APIs. In the end, it's just docker plus a bunch of scripts.