Dropping native Heroku support

It was discovered today that Heroku could be changing their pricing structure. Of course, we understand the reasons for this; a company needs to make money and can't have a load of people free-loading off of their services.

Why does this affect Cachet?

Cachet is one of the few services out there, at least that we've seen which makes use of the Heroku Button, better known as the Deploy to Heroku button that you see in the Cachet repository.

Very early on we added native Heroku support to Cachet as it allows anybody to deploy an instance of it for free and with very little experience in web applications.

With just a Heroku account and a couple of minutes spare, you too could have your very own status page, completely free and independent of any other hosting providers you may use.

This new pricing structure changes this: Heroku's free accounts are no longer viable when running an application such as Cachet.

What's happening with Cachet?

We're going to be completely removing support for Heroku deployment out of the box. You will still be able to manually configure Cachet to work with Heroku and the Postgresql addon, but there will be no "one click" way of doing this.

Is that the only reason?

Honestly, no.

  1. I've had absolutely no support from Heroku in regards to implementing and improving deployments with the Heroku button. I Tweeted, emailed and mentioned via GitHub issues, but had absolutely zero response from them. Considering the amount of deployments to Heroku we must've made from Cachet itself, you'd think they'd be inclined to support us - especially since some of those deployments could genuinely turn to paid tiers.
  2. Laravel 5 doesn't support the same per-environment-configuration as 4 does. This means that we're unable to provide a heroku-specific configuration file for deployments. Whilst this may change in 5.1, we can't wait for that to land before shipping Version 1 of Cachet.

What are my options?

  1. You can deploy Cachet to a DigitalOcean account for at least $5 a month. If you choose to do this, we'd love for you to support development and server hosting costs for Cachet by using our referral code - this helps both us and yourselves out. This is the option that we will be taking for both the Demo and Cachet's own status page.
  2. You can use OpenShift. @StartedPhoenix has provided a clever way of running Cachet on OpenShift too.
  3. Use any other web host you like.
  4. Run a Dokku instance on another server, this is very similar to running and deploying to Heroku, but without the button.

We're sorry if this effects you, it's both frustrating and upsetting to pull a feature that has been critical to Cachet's success, however we hope that you understand our reasoning behind this decision and continue to support us as we go.

You can follow the progress of this change in issue #557, which can be found in our issue tracker.

Share Comment on Twitter