Heroku Button

[marceloboeira]

Since the service is very decoupled from the rest of the infrastructure, it could be nice to be able to start an instance on Heroku (isolated infra) to monitor.

More info at:
https://blog.heroku.com/heroku-button
https://devcenter.heroku.com/articles/heroku-button

[jbrooksuk]

Personally, I'd never do this again... https://blog.alt-three.com/dropping-native-heroku-support/

[freibuis]

heroku for me is all about disconnection... its not on our infrastructure... its dirt cheap (zero cost if you are having no issues lol)

[jbrooksuk]

On the free tier, you don't (at least didn't get 24/7 availability) which defeats the purpose of a status page...

[marceloboeira]

its not on our infrastructure

In general, I don't find a good practice to monitor your infra using your own infra...

[marceloboeira]

On the free tier, you don't (at least didn't get 24/7 availability) which defeats the purpose of a status page...

You get 1000 hours per month on the free tier. Which is much more than you need to monitor another app...

[freibuis]

the only problem with the free tier is the worker (for email) will not work..
so if you dont want to pay for a status page and you hardly ever have any outages it will cost you nothing.... just pay when you have an issue... its only 7$. boom

[marceloboeira]

@freibuis the free tier allows you to use multiple processes now. I have one app running on free tier with sidekiq.

[freibuis]

@marceloboeira wow. didnt know.... 🤔 this could be dangerous :)

[ideasasylum]

@marceloboeira Here's a fork I hacked together that's deployable using the Heroku button. You can see the PR for more details in what I needed to change