| ▲ | scott_w a day ago | |||||||||||||||||||||||||||||||
A Django+Celery app behind Nginx back in the day. Most maintenance would be discovering a new failure mode: - certificates not being renewed in time - Celery eating up all RAM and having to be recycled - RabbitMQ getting blocked requiring a forced restart - random issues with Postgres that usually required a hard restart of PG (running low on RAM maybe?) - configs having issues - running out of inodes - DNS not updating when upgrading to a new server (no CDN at the time) - data centre going down, taking the provider’s email support with it (yes, really) Bear in mind I’m going back a decade now, my memory is rusty. Each issue was solvable but each would happen at random and even mitigating them was time that I (a single dev) was not spending on new features or fixing bugs. | ||||||||||||||||||||||||||||||||
| ▲ | pinkgolem a day ago | parent [-] | |||||||||||||||||||||||||||||||
I mean, going back a decade might be part of the reason? Configs having issues is like number 1 reason i like the setup so much.. I can configure everything on my local machine and test here, and then just deploy it to a server the same way. I do not have to build a local setup, and then a remote one | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||