Recently I have been working on increasingly complex Rails apps and have been looking for a way to better handle deploying them. That being said, these are apps that only a handful of people are using and are all hosted on Heroku.
The following is the recipe I have pulled together to take the deployment of
these apps a bit more seriously while not making it too complilcated. Think
$ git push heroku meets
$ cap deploy.
NOTE: This post is a work in progress and currently just acting as a placeholder. Check back soon for more.
The following are the slides I used to present this talk at the September 2012 BostonRB lightning talks meeup. After the slides is a bit more detail.
Jasminerice integrates the asset pipeline into the jasmine testing flow.
By default, the test environment is set to swallow up parsing errors encountered
while working through an asset file. This can cause the
guard-jasmine task to
incorrectly report a pass with 0 test, 0 failures. In order to avoid this, set
config.assets.debug = true in test.rb environment file. The details of this
issue can be found here.
Full Stacking It
Heroku use this rake task
Travis drop the following in as your travis test task
1 2 3 4 5
1 2 3 4 5 6 7 8