Hi jef, jef wrote: > > I am developping a web app and I've wrote some admin > code (parsing web site, sending massmail etc...) which don't > need to be deployed. So I would like this code to be part of > a second developement app.
Interesting. What leads you to want to separate the admin functionality into a completely separate app? > But there's a probleme regarding the schema_migrations table. > it must be unique. > > How can I solve this problem? The easiest way I can think of would be to simply run all your migrations from one of the apps. As long as you never run any migrations from the second app I can't think of any way you'd run into conflicts. Doesn't mean you won't. Just that I can't think of any off the top of my head ;-) HTH, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
