My website crashed for 12 hours 😭

ton of things, outside of the obvious of just testing your shit after you deploy it (you mentioned it being carelessness on your end, and you're definitely correct).

a few things I do, and you may or may not be doing some or all of this already:

1. use a CI/CD pipeline and don't do manual deploys / allow yourself easy access to get code to production outside of the automation
2. automatically lint your code as part of your CI/CD pipeline. depending on the language and styleguide in place, this can shake out an epic amount of problems (typescript + airbnb styleguide being my stack du jour)
3. write tests to help ensure things are as they should be, also running in your CI/CD
4. add some sort of monitoring to ensure your app is at the very least serving a 2xx code
5. add something like sentry or new relic to do more advanced monitoring for issues.

Use https://uptimerobot.com/

It's free and very simple to setup. It will take you 5 minutes and it's saved my butt several times

Hi @Damon,

Downtime is something nobody really wants to have. :/

I'd be happy to grant you free access to the API monitoring service I'm developing. Hit me up if you're interested.

https://www.indiehackers.com/post/monitoring-your-api-for-free-4a0f12740c

should really push to stage env and if it works deploy to production

Hey, @damon

I'm glad you resolved it! Better late than never 😁Kudos to the guys 🙌✨

I've prepared this one for you:

📢 https://hostedstatus.page/lonely.dev

You can monitor your website for any response time issues and 💥downtime 💥. It's not like the Sentry, but it works just like any other monitor - you get an email when the sh1t goes south 😁

Anyway, its main purpose are incident reports. It's still in private beta, but you can enjoy the downtime detection for now. You can ping me at dragstor+ih@gmail.com so I can set up your account, should you need it 😊

Cheers!
~N