-
-
Save mjhea0/8656231 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| These links: | |
| http://help.nitrous.io/heroku/ and | |
| http://help.nitrous.io/heroku-rails/ | |
| are good, but they're missing some information for deploying simple apps to Heroku. | |
| This assumes that you already have Git and GitHub set up on Nitrous.io and you've been | |
| pushing your code to GitHub throughout development. | |
| -Do the first five steps of this page: http://help.nitrous.io/heroku/. Skip the rest | |
| of the steps. | |
| -Do the steps under "Deploy to Heroku" on this page: http://help.nitrous.io/heroku-rails/. | |
| Note that if you want to give your app a custom name (as opposed to the random name that | |
| is generated), you can run "heroku create [appname]". App names must be unique so you'll | |
| get an error if the name is already taken. Then do "git push heroku master". | |
| -After Heroku deployment, you need to run a few rake commands if you have a database | |
| component to your Rails app: | |
| - heroku run rake db:migrate | |
| - heroku run rake db:seed (if you're using faker for test data in production) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment