Best practice to continuously integrate application updates
matthew.bruzek at canonical.com
Wed Jul 2 14:32:09 UTC 2014
Thanks for the email. You are correct that you would use the "juju
upgrade-charm" command to update the contents of your web application. You
would implement the upgrade-charm hook to do what is necessary to update
your web application.
There is an excellent example of an existing charm written by Robert Ayres
that you can look at here:
If you have charm tools installed you can download this example to your
juju charm get cs:~robert-ayres/precise/j2ee-deployer
The README file details how you can use the j2ee-deployer charm to deploy
webapps and update them as necessary. This would be a great model to use
for your own charm.
Let me know if you need any more help on this!
- Matt Bruzek <matthew.bruzek at canonical.com>
On Tue, Jul 1, 2014 at 9:47 PM, Denis Weerasiri <ddweerasiri at gmail.com>
> I mentioned the command as "charm-update". But it should have been
> On Wed, Jul 2, 2014 at 12:44 PM, Denis Weerasiri <ddweerasiri at gmail.com>
>> Support I have written a charm to deploy a web application on top of
>> tomcat. And now I need to redeploy the web application when I update the
>> source repository of the web application. What is the best practice to do
>> What I have in mind is to write a new version of charm and use
>> charm-update command. So juju will re-deploy the web application.
>> Denis Weerasiri
>> Sent from my iPhone
> Denis Weerasiri
> Sent from my iPhone
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju