rake db:schema:load instead of rake db:migrate in your production server. On Fri, Nov 27, 2009 at 12:44 PM, Hassan Schroeder < [email protected]> wrote:
> On Thu, Nov 26, 2009 at 11:33 AM, Conrad Taylor <[email protected]> > wrote: > > > Michael, why don't you simply use the glassfish gem for deployment? > > It's not always suitable, especially if you have an existing Tomcat > installation with other non-JRuby apps. > > > In any cade, if you're trying to update the schema on the production > > machine, the you can simply do the following: > > > > rake db:migrate RAILS_ENV=production > > No, you can't; that's the whole point -- none of those rake tasks are > packaged with the WAR file. > > The legacy app I inherited uses Capistrano to check out and deploy > a JRuby app in standard Rails format, which is useful for running > migrations, scripts via cron jobs, etc., and then builds and deploys > the WAR file from there. > > It seems a little redundant, but it works :-) > > FWIW, > -- > Hassan Schroeder ------------------------ [email protected] > twitter: @hassan > > -- > > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > > -- Liu Lantao College of Information Science and Technology, Beijing Normal University EMAIL: liulantao ( at ) gmail ( dot ) com ; WEBSITE: http://www.liulantao.com/ . ------ -- 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.
