Db create and migrate from war

Hi there. I’ve successfully packaged up my Rails app with Warbler and
deploy it on Tomcat 5.5. Next, I’d like to ship it to my customer with
a minimal set of installation instructions. Ideally, it would be “drop
war in webapps/”, but something more involved is fine.

My main question is how to go about doing the database initialization.
It seems silly to require them to install jruby and gems just to run
“rake db:migrate” when JRuby and all the gems are already sitting there
in the WEB-INF folder. I’ve played around a bit with “jruby-complete
–command …” which seems to be going in the right direction. Is there
a way to point jruby-complete to the gems (rails, jdbc and rake, mostly)
that I already have in WEB-INF/gems?

I’m new to almost all of this so feel free to let me know if I’m going
about it completely wrong.

Thanks,
Dave


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Once the war file is expanded, I’d think you could do something like
you’re trying to do.

We wanted to avoid making the hosting company have to run anything on
the command line, so we created a “setup” controller to run the
migrations. And, because we didn’t want the app to use a db login with
admin-level access, we created a separate environment for the setup
controller to run with, and a separate jdbc pool for the setup db login.
In order to ensure that the internet didn’t have DB migration powers, we
set up the setup controller to return 404 if there were no migrations to
run, and we used a FS-based authentication mechanism (the app creates a
temp file, and tells the user to put a hash into the temp file) that
I’ve seen other web apps use.


Matt

Dave Ray wrote:

a way to point jruby-complete to the gems (rails, jdbc and rake, mostly)

http://xircles.codehaus.org/manage_email


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs