Join Newsletter


Share with:

Recent Posts

Heroku Tag

Nonschema migrations version 5.0.0: RubyGems Page, GitHub page Now compatible with Rails 6, nonschema_migrations is the best way to separate your schema changes from your data changes. Want to run no-downtime deploys with data-only migrations? No problem. Install it in your Rails app today to see...

Read More

Although Heroku has put a lot of attention into their own Postgres-based datbase architecture, Heroku Data, this article still works for rebels who want to use Amazon RDS on Heroku: Note that I can't seem to get "sslca" to work as a config option in my...

Read More

This is to fix build, slug, and caching problems related to asset compilation during slug compilation. Everyone needs a little spring cleaning, right? No, really. Sometimes when I switch around buildpacks or change up assets I run into a strange asset cache problem. Here's the...

Read More

First you need to know how to connect to your Heroku application using bash. You can then use the du -h command to get a read on how big the files inside your slug are. heroku run bash -a yourappname Once you've done that, here's the magic...

Read More

What you may miss off-the-bat is that Heroku's copy of your app is actually a git repository. It's like github's repository of your code, but it is used for the special purpose of deploying the app. When you do a deploy to Heroku, you are...

Read More

Ran into an annoying chicken/egg involving deploying to Heroku with a shared database. It seems that Heroku isn’t happy unless you have gem ‘pg’ in your Gemfile. If you are using the shared database and fail to have gem ‘pg’ in your Gemfile, you app actually deploys OK on Heroku but then generates an Application Error when you call a page. If you check the heroku logs you see something like this: