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

[Adam Collard]

Is this location still controllable through the JUJU_HOME environment
variable?

On Mon, 8 Feb 2016 at 07:16 Ian Booth <ian.booth at canonical.com> 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 XDG desktop
> standard
> and use this directory (by default):
>
> ~/.local/share/juju
>
> to store its working files (%APPDATA%/Juju on Windows). This is partly to
> allow
> Juju 2.0 to be installed alongside 1.x.
>
> Very, very soon, the need for an environments.yaml file will be no more,
> meaning
> there will be no need for the user to edit any files in that directory. As
> a
> sneak peak of what is coming, you will be able to, out of the box:
>
> $ juju bootstrap mycontroller aws/us-west-2
>
> Note that there's no need to "$ juju init" or edit any environment.yaml to
> use
> the public clouds and regions supported by Juju. Adding support for new
> regions
> or cloud information is a simple matter of running "$juju update-clouds".
> There's more to come, but you get the idea.
>
> Anyway, the point of the above is to say the location of the home/data
> directory
> doesn't really matter as there will be no need to poke around inside it.
>
> As an interim measure, if you run off master, just:
>
> mkdir ~/.local/share/juju
> cp -r ~/.juju/* ~/.local/share/juju
>
> if you want to use existing models with the latest build from source.
>
>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160208/feb6409b/attachment.html>