Re: Use of Jujucharms to launch non-opensource code

Hi Marco, It is the former. Using Juju and charms in a commercial project/product. regards Ramesh On Sun, 7 Feb 2016 at 20:11 Marco Ceppi wrote: > Could you elaborate on your usage? Are you wrapping Juju itself in a > commercial project, using the charms in a

Re: Breaking news - New Juju 2.0 home^H^H^H^H data location

Is this location still controllable through the JUJU_HOME environment variable? On Mon, 8 Feb 2016 at 07:16 Ian Booth wrote: > As advance notice, the next alpha release of Juju 2.0 (due this week) will > use a > new default home location. Juju will now adhere to the the

Re: Breaking news - New Juju 2.0 home^H^H^H^H data location

Does this mean the environments.yaml file is going away at some point? On Mon, Feb 8, 2016 at 10:33 AM, Adam Stokes wrote: > Does this mean the environments.yaml file is going away at some point? > > On Mon, Feb 8, 2016 at 2:16 AM, Ian Booth

Re: Breaking news - New Juju 2.0 home^H^H^H^H data location

Yes >> Very, very soon, the need for an environments.yaml file will be no more, Hopefully in time for the 2.0 beta due sometime next week. On 09/02/16 01:33, Adam Stokes wrote: > Does this mean the environments.yaml file is going away at some point? > > On Mon, Feb 8, 2016 at 2:16 AM, Ian

Re: Use of Jujucharms to launch non-opensource code

IANAL either, but if you are just using Juju and public charms to deploy a commercial project or product, then I think that is fine. Like deploying a private django app (which is what I do). This is just using the tools for what they were designed for. However, if you are modifying Juju source,

Re: Use of Jujucharms to launch non-opensource code

Also I would assume your charm code only needs to be open source if you are uploading it to the store. Local deployment etc wouldn't apply... -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart