cangevine/STEAMnet — pull request #60 by maxluzuriaga (2013-07-10 20:52:01+00:00)
Title: Heroku Rails 4 Fixes (Already pushed to heroku)

This is basically me jumping through some bizarre hoops to get my previous Rails 4 upgrade code to work on Heroku.

I've already pushed this up to Heroku, and it's working fine now, but I think the system we'll want going forward is that I won't push any code up to Heroku until the associated pull request is accepted into your "master" repository, BC. From that point I can handle deploying the code to Heroku, and dealing with any errors that show up from doing that.

This way the production code will always mirror the master repository, which gives everybody else a chance to look at and then accept or reject my changes to the API before they go live.

Of course, this particular pull request has already been pushed to Heroku, but I'd call this one the exception, because without it the server would crash on start.