Multi-War Deployment?

We want to package our app as a single, versioned, easy-to-deploy
artifact for our customers.

However, we use solr for search in our app, and we’re wondering how
this will work, since solr is packaged in its own war file, and needs
an app-specific schema config file (which changes as the app evolves).

How would you approach this? Here’s some options, advice on the best
one or others is welcome:

  1. Deploy separate war files, one for the app and one for solr? In
    this case, where does the schema file live? We could rebuild the Solr
    war with our schema file on every deploy, but it seems wrong to
    repackage solr for that purpose. Or we could have the schema file be
    a flat file on the system. Either way, the customer will have to
    manage multiple artifacts on deploys.

  2. Package the app as an EAR? Packaging multiple wars and configs is
    the purpose of EAR files, but I see very little mention of EARs +
    Jruby on the web.

Thanks,
– Chad


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Hi Chad. We use solr in our app as well – we’ve deployed it as a
separate war app. The solr.war app doesn’t need to be changed very
much so we leave that outside of our standard app deployment. For
deploying the rails app, we use capistrano with some added hooks that
call warbler to war up the app then deploy it to the app server. The
benefit of this is that it’s easy to revert to a previous deploy and
it’s similar to a standard rails deployment.

Rich

On Sep 29, 2009, at 10:05 AM, Chad W. wrote:

  1. Deploy separate war files, one for the app and one for solr? In
    Thanks,
    – Chad

To unsubscribe from this list, please visit:

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