4 ms·
Ask HN: Checklist for starting a new Rails application?
It's easy to create a new Rails application using "rails new myapp" (or using an application template). But after that, what do you do? What gems do you always add? What decisions do you make before beginning development? What important items are often overlooked before deploying an app? I'd like to put together a reference checklist to share. Any suggestions?
For example:
- Create a new RVM gemset
- Modify the .gitignore file
- Switch from TestUnit to RSpec
- Set up Guard to run tests in the background during development
- Add the viewport metatag to the default application layout
- Don't forget to create a sitemap.xml file
- Add a Google Analytics snippet
What else?
- rpwilcox 15y agoI always add Cucumber, Machinist, Omniauth + devise, formtastic, show_for, foreman, and (lately) the twitter-bootstrap-rails gem
- aliukani 15y agoI'd like to hear more about your setup. Why do you consider these essential?
- dholowiski 15y agoI definitely second Omniauth+devise - my go-to for Authentication.
- goshakkk 15y agoIf you love Cucumber, you definitely should take a look at Spinach: http://codegram.github.com/spinach/ http://codegram.github.com/spinach/
- clyfe 15y agoSome from my stack (vary based on project): Devise, CanCan, sentient_user, CarrierWave rails_config, rails-settings ActiveScaffold Rspec, Capybara, Spork, Guard, factory_girl, faker capistrano