Not sure if it's useful information or not, but in the repository I use for engines, I've made it simply use the current Rails migration mechanism, ie, no generator is required, the migrations in plugins are automatically ran.
My repository is way out of date though... I should really do a pull to see if it works just fine with the recent changes. Miles On Mon, Sep 7, 2009 at 2:03 PM, Cynthia Kiser <[email protected]> wrote: > Quoting Andrew Roth <[email protected]>: >> James, on your presentation at railsconf ( >> http://rails-engines.org/news/2009/05/18/engines-at-railsconf/) you suggest >> (for now) making your own generator to handle the migrations issue. Can you >> elaborate on that method? > > I am not James - but I recently needed something like that. I used the > Clearance engine as a model for buillding the migrations I wanted. > > http://github.com/thoughtbot/clearance/tree/master > > James, is there video anywhere of your talk? I got a lot out of the > slides but there are a couple where I would like more detail as was > probably provided at the talk. > -- > Cynthia Kiser > > _______________________________________________ > Engine-Developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > _______________________________________________ Engine-Developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
