undefined | Better HN

0 pointsornornor27d ago0 comments

That’s neat. How do you handle the rest:

- backups - upgrades to the os packages (and downtime from reboots) - updates to container images (if you run any) - monitoring and alerting (logs, http 500 increase, http 200 drop, etc)

Asking because I’m looking for pointers on how to solve this myself when deploying to a VPS rather than AWS alphabet soup or a PaaS

0 comments

xxxxxxxx25d ago

I don't use containers. I just use systemd / systemctl to run the go apps. I manually update Debian on a schedule I keep. For logs I just ship them to my own app I developed that send messages to a discord server - but I might switch that over to something better one day but it's okay for now. I pay a little extra for Linode backups and have had to use it once, any anything important I backup to S3 and/or locally. I also forgot to say I also use SQLC - so I never have any issues with SQL being wrong or out of sync with the data model.

j / k navigate · click thread line to collapse

0 comments

xxxxxxxx25d ago

j / k navigate · click thread line to collapse