Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Rails application recipes

#160

I'm wondering if you considered some kind of recipe for Rails applications. Every time we start a new Rails project in our company, we are taking the same steps: installing certain plugins, adding some custom rake tasks and executing svn actions to create a proper svn workspace. Wouldn't it be nice to apply some kind of application recipe when generating a new application with the 'rails' command?

The guys from Caboose created the Sample Rails application, which can be retrieved from SVN. I don't think storing a sample application in SVN is such a good idea, because of the versioning of the Rails code and plugins. When creating a new project, I often want the lastest Rails version and the most recent plugins and not be forced to update the sample repository first.

A recipe in the simplest form should contain a number of commands to execute, e.g.:

script/plugin install rspec
script/plugin install rspec_rails
rake svn:configure

In this way, the problem can easily be solved with a bash script. But I think a more high-level (YAML?) solution could also be nice:

plugins:
    rspec
    rspec_Rails
tasks:
    svn:configure

This recipe file should be passed as an argument to the rails script:

rails weblog --recipe=/home/edwin/rails_with_rspec.yaml

It is even possible to make it possible to give an URL as argument, but this might be a bit overkill. It can be nice though when someone wants to share his recipes or to share recipes within a company.

I'm willing to add the functionality to the Rails core with a patch, but would like to know if it is a feature that fits in the Rails vision and if more people think this is usable.

Reported by Edwin Vlieg · May 9th, 2008 @ 10:01 PM

State: invalid
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. DHH
    DHH
    • State changed from new to invalid

    I think this is rather specific to a certain use case (many applications using exactly the same setup). I think it'd work better as a plugin for starters.

    May 11th, 2008 @ 07:45 PM

  2. Edwin Vlieg
    Edwin Vlieg

    I don't totally agree with you David. It is not the case that many of my applications are using the same setup. I'm using for example RSpec and whatever the content or setup of the application I'm building is, I need the plugins. The same for plugins as exception_notification or mail_queue.

    But I do agree with you on your other point, a plugin would be a good starting solution as long as it is not sure more people are experiencing this problem.

    May 11th, 2008 @ 07:54 PM

  3. Courtenay
    Courtenay

    Or, you could keep your blank-state application in Git, which would solve the upstream issue.

    May 11th, 2008 @ 08:21 PM

  4. Sven Fuchs
    Sven Fuchs

    How about a bash script? Or a rake task?

    May 11th, 2008 @ 09:38 PM