Rather than Haml, at this point, I'd use Slim. Slim is cleaner (I'd say nicer) and faster than haml.<p><a href="http://slim-lang.com/" rel="nofollow">http://slim-lang.com/</a>
Great! Also see Thoughtbot Suspenders, <a href="https://github.com/thoughtbot/suspenders" rel="nofollow">https://github.com/thoughtbot/suspenders</a><p>It also uses Bourbon, HAML, RSpec, etc. as well as many more gems. Overall I like and recommend what Thoughtbot creates.
I've added this to the list of application templates I track at <a href="http://railsapps.github.io/rails-application-templates.html" rel="nofollow">http://railsapps.github.io/rails-application-templates.html</a>.<p>There's also a list of starter apps at <a href="http://railsapps.github.io/rails-examples-tutorials.html" rel="nofollow">http://railsapps.github.io/rails-examples-tutorials.html</a>.<p>Most starter app projects end up as abandonware as Rails changes so it's good to see a new app template offered for Rails 4.0. Starter apps always produce a great discussion about must-have gems.
For development I have become cracked out on these for all of my apps<p><pre><code> group :development do
gem 'better_errors' #literally what it says
gem 'binding_of_caller' #adds REPL to better_errors
gem 'quiet_assets' #prevent asset pipeline log doesnt go to console
gem 'guard-livereload' #adds live reload
gem 'rack-livereload'
gem 'meta_request' #chrome rails panel extension
end</code></pre>
I have a starter app based on Ruby 2.0, Rails 4.0, PostgreSQL, Bootstrap and OmniAuth. Deployable on Heroku.<p>Here is what it looks like running live: <a href="http://frozen-savannah-6000.herokuapp.com/" rel="nofollow">http://frozen-savannah-6000.herokuapp.com/</a>
> Remove the require_tree directives from the sass and JS files. It's better design to import or require things manually.<p>I'm sorry, what?
Nice template, looks like an opinionated one . I see you have used ".env" file. I read somewhere when opensourcing apps its better to have all the env variables in .env, instead of using gem like <a href="https://github.com/laserlemon/figaro" rel="nofollow">https://github.com/laserlemon/figaro</a>.<p>Also there is rails_composer <a href="https://github.com/RailsApps/rails-composer/" rel="nofollow">https://github.com/RailsApps/rails-composer/</a> with many options to select css framework, servers, testing tools.
I just love GitHub. Followed the link, noticed that certain links were highlighted as links but not working. Went to the README, edited the broken links, sent a pull request [1], and now it works as expected. Everything done without having to leave "browsing mode", i.e. no cloning, no terminal, no editor.<p>[1] <a href="https://github.com/dennybritz/rails_startup_template/pull/3" rel="nofollow">https://github.com/dennybritz/rails_startup_template/pull/3</a>
So, I did something similar, and I found that one of my least favorite things was going into the browser to create and link the github repo. Using the octokit gem, I automated that part. Feel free to swipe some code from my gist:<p><a href="https://gist.github.com/BrainScraps/5952463" rel="nofollow">https://gist.github.com/BrainScraps/5952463</a><p>Rock on.
Why not make a switch gems, in case someone doesn't want them? In other words, something like:<p>ENV['dont_include']='bourbon,analytics-ruby' rails new [app-name] -m template.rb