I don't disagree with the article's main sentiment. You don't always need AWS. I advocate quite a bit for self-hosting when it makes sense. But if you're going

I don't disagree with the article's main sentiment. You don't always need AWS. I advocate quite a bit for self-hosting when it makes sense. But if you're going to manage your own servers, you need to do it right. This article is a perfect example of what I've seen in the past with not doing it right. It's inconsistent, it doesn't take backup seriously, and it doesn't take availability seriously. Postgres is installed from their repo. Caddy is installed via & managed via ansible (instead of using something like caddy-docker-proxy). Actual backends are managed via docker compose. Backups are via a hacky script instead of something maintained & that another developer will be able to find docs on like borgmatic. Nothing is thought about for making sure the database state is consistent during backups (eg barman). Monitoring is an afterthought. Firewalling isn't even mentioned. This setup is one hardware failure away from spending days or weeks trying to recover.