Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Why is my production application that was healthy in production returning 404s when a rollback deploy fails?
I originally had a healthy application deployed to Digital Ocean Apps. I created a new deploy, which failed. This caused a rollback deploy to occur. This rollback also failed.
about 9 hours ago Error Automated rollback after failed deployment of "073dc20c-3910-42ca-aaeb-4c47c545ef3f" Details about 9 hours ago Error Commit 6c543f6 pushed to gitlab.com/...
At this time the live production app starts throwing 404s and is effectively taken offline. I am now forced to do a manual deploy to get my app running again.
Why is this the default functionality for deploys? I have health checks for a reason. My production containers should never be touched unless the deploy is successful. Is this not the case? If so it needs to be made very clear in big bold letters everywhere.