[chef] Re: Re: example using application_java?

[Jesse Campbell < >]

We deploy our rails apps in war/java containers using something called
Warbler (this comes from the developers, I haven't investigated it
myself). The dev group wants us to implement capistrano, but i feel
like that is like saying we should use puppet for this one thing...
we're a chef shop, do it the chef way is how I want to respond... but
so far I haven't found what i need.
We may continue using Bryan's tomcat6, and use his maven LWRP for
deploying the wars... but i think even that may leave us without a
migrations plan...
perhaps there is a way to use some aspects of the deploy resource to
orchestrate migrations... i'll investigate later in the week (for now
I just need to get things running once to get the PMs off my back).

-Jesse

On Tue, May 29, 2012 at 4:20 PM, Andrea Campi
<
 >
 wrote:
> Jesse,
>
> On Tue, May 29, 2012 at 9:11 PM, Jesse Campbell 
> <
 >
>  wrote:
>> Does anyone have an example that uses application_java?
>> We are deploying about 15 different war files into tomcat from a maven
>> repository (running nexus), there is a DB role that would need rails
>> migrations performed.
>> There is a simple example for deploying jenkins, but it doesn't get
>> into migrations at all..
>>
>> We're currently deploying tomcat with the tomcat6 cookbook, dropping
>> the dependent jar files in with our own custom cookbook as we'd
>> originally wanted to avoid the methods that the tomcat and java
>> cookbook used for jar distribution.
>
> documentation can/should be improved, but there is something in the
> application cookbook.
> There is nothing framework-specific to migrations anyway; as many
> other feature in the application cookbook, it maps directly to the
> deploy resource; its documentation applies.
>
> Except... the Java cookbook does not use deploy at this time; it
> didn't in the previous version, and unfortunately it still does not.
>
> It's not very clear to me how migrations would fit in the workflow of
> a typical Java shop. In fact I've brainstormed about application_java
> with miscellaneous people and we haven't even touched on
> migrations--not high-priority enough, I guess.
>
> I'm curious: you mention Rails migrations? Do you also have a Rails
> app, or do you use it just for managing migrations?
> Could you maybe use application_ruby for that part, and then somehow
> orchestrate the deployment interactions?
>
> Andrea