How to Deploy your First Rails App: New on Premium
plusvideos

How to Deploy your First Rails App: New on Premium

Tutorial Details
  • Availability: Premium Exclusive
  • Format: 15 Minute Screencast
  • Post Image: Available on GraphicRiver
Download Source Files

In this Premium video tutorial, we’ll teach you how to deploy your first Rails web application with Heroku. Particularly if you’re somewhat new to Rails, you may find that you’re met with a long string of errors when pushing your app and database to their servers. Don’t worry, though; this screencast will take you through the entire process from scratch.

Become a Premium member to watch this video, as well as hundreds of other advanced tutorials and screencasts from the Tuts+ network.


You’ll Learn How To…

  • Work with models and controllers
  • Adjust routes
  • Source control with Git
  • Install and work with Heroku
  • Convert a Sqlite3 database to PostgreSQL
  • Debugging Heroku errors

Add Comment

Discussion 22 Comments

  1. Rahul says:

    Now I gotta get a premier membership..

  2. Ethan says:

    @Jeffrey will this be available on the tuts+ market place?

  3. i need to renew my premium membership!

  4. Bazhan Denis says:

    Why on heroku better to Rackspacecloud. Heroku a lot of lessons. 8(

  5. Andre Dublin says:

    Great tutorial Jeff, would there be a possible future for explaining the Passenger gem (mod_rails) for launching on Apache servers?

    • Baylor Rae' says:

      +1. Deploying on Heroku should not be a premium tutorial.

      • Agreed. If you can figure out how to commit to Github, you can deploy to Heroku.

      • Jeffrey Way says:
        Author

        That’s not true at all — especially if you’re new to Heroku. Those guys won’t realize that they don’t, for example, support Sqlite databases, or how to perform migrations on Heroku, or how to convert their table data to a different format with the Taps gem, or how to debug Heroku issues in general.

        If you know how to do those things already, fantastic — this tutorial isn’t for you.

      • Ethan Kramer says:

        @Jeffrey I want to learn how to do this for new app <a href=”http://forrst.com/posts/WIP_A_Sneak_Peak_At_My_New_Service_EDDITT-9vZ”>edditt<\a> which will based off Rails. I am willing to pay for a tutorial on the tuts+ market place. But i don’t want to tie myself into monthly plan (mostly because i can’t afford to). Like i said earlier, would love for you to put this on the tuts+ market place like you have done with some of your other premium tutorials

      • Baylor Rae' says:

        Jeffrey you’re right to a degree. I’m still very new to rails and Heroku, but I was able to move my database over with the Heroku documentation.

        It’s all right here
        http://devcenter.heroku.com/articles/rails3


        To be clear, I’m not dissing your tutorial or its content. In fact, I considered buying it through the Tuts+ Marketplace. But the “what’s covered” list is almost completely available in Heroku’s documentation and a quick google search which makes me question the level of premium content being delivered.

      • Jeffrey Way says:
        Author

        I’m right completely. Sure, the “refer to the documentation” argument can be used for most tutorials. Some people need a more visual tutorial to work through these new technologies and such. If you’re not one of those people, fantastic. This tutorial is not meant for you.

        It’s like me commenting on a “Get Started With jQuery” tutorial, and noting that most of the information can be found in the jQuery documentation. Well yeah! Obviously that’s true. But documentation is often a bit more sterile and confusing.

      • Jeffrey Way says:
        Author

        You can’t make assumptions that everyone is familiar with Git, and GitHub, and Heroku, and Rails, and the command line.

      • Jeffrey, I totally appreciate your perspective. If I would have taken a moment to collect my thoughts the other day, I might have said something more along the lines of… it’d be cool to see a tutorial that covers common issues a beginner might face using Passenger to deploy on a VPS. Heroku is cool for deploying a tutorial app quickly for free, but can get extremely expensive with actual production apps. I’ve heard good things about Engine Yard’s Cloud service as well, but I’ve never used it.

      • Jeffrey Way says:
        Author

        I have a Passenger tutorial in my author-recommendations list. :)

      • Baylor Rae' says:

        You’re right. I did make the assumption that everyone is familiar with Git and command line. But I do think my point “I’m questioning the level of premium content being delivered” still stands. The only reason I posted my comment, which I never intended to debate over, was that Heroku is super easy to use and I didn’t understand why this was a premium tutorial.

      • Rory says:

        “It’s like me commenting on a “Get Started With jQuery” tutorial, and noting that most of the information can be found in the jQuery documentation. Well yeah! Obviously that’s true. But documentation is often a bit more sterile and confusing.”

        This. This, and this again. This is the sole reason I purchase and read your articles. Having you narrate what’s going on and dropping nuggets of wisdom every so often tops any 20 page doc that assumes a familiarity with whatever it is you’re doing.

        Thanks again

  6. Joris Ooms says:

    Thanks Jeffrey! More Ruby on Rails tutorials please, premium or normal doesn’t matter ;)

  7. Vezu says:

    I deployed my first rails application on heroku. Took me three days to figure it out. lol. http://www.stagesong.com/

  8. Baylor Rae' says:

    Are you planning on adding this to the Tuts+ Marketplace? And do you think you’ll ever a tutorial on deploying to something like Linode?

  9. Robbie Done says:

    Great tutorial, there is nothing out there that i could find that showed you how to migrate to postgres, well done :)

Add a Comment

To add a code snippet to your comment, please wrap your code like so: <pre name="code" class="html">YOUR CODE</pre>. You can replace the class name with "js," "css," "sql," or "php." If there are any "<" or ">" within your code, please search and replace them with: &lt; and &gt; respectively.