<p>Let's say you want to create a new Rails app. Every time you run "rails my_app" you usually also do some other steps such as:</p> <pre><code> # You need to remove the index.html for your app to work: rm public/index.html # Maybe you also create some basic Models everytime: ./script/generate scaffold person name:string # Adding a route to the homepage # route "map.root :controller => :person" # Migrating the database rake db:migrate # The first commit in Git git init git add . git commit -a -m 'Initial commit' </code></pre> <p>This problem's gone. Edge Rails now supports a solution using "Templates". Running a command like this:</p> <pre><code> rails blog -m ~/template.rb </code></pre> <p>You're passing parameters to the 'rails' command, telling everything it needs to be done after the creation of the app directory. Things like installing plugins, removing files, putting some default css and image files in /public, the works! So, inside the template.rb file you'd put something like this:</p> <pre><code class="ruby"> # template.rb run "rm public/index.html" generate(:scaffold, "person name:string") route "map.root :controller => :person" rake("db:migrate") git :init git :add => "." git :commit => "-a -m 'Initial commit'" </code></pre> <p>Cool, isn't? :)</p> <p>Better yet, you can use an URL to the rails command, so from any machine you're using you'll always have the initialization commands at your disposal. How great is that? :)</p> <pre><code> rails blog -m http://gist.github.com/31208.txt </code></pre> <p>For more information on Rails Templates check <a href="http://m.onkey.org/2008/12/4/rails-templates">here</a> and <a href="http://omgbloglol.com/rejoice-rg-is-now-part-of-rail">here</a>.</p> 236 2008-12-04T12:52:45Z 10 rails-templates 2008-12-04T13:00:41Z