On 16/08/16 07:19, Alexander Taler wrote:
> - Handling a variable number of files, such as code which can
>have arbitrary dependencies. They could be combined into a
>single archive, but that makes versioning difficult.
> - Handling third party packaging and installation tools like npm
>
Thanks for pointing that out Tim.
Resources look good for basic use cases, with a small number of
files, but there are a couple of scenarios which I don't think it
would handle well:
- Handling a variable number of files, such as code which can
have arbitrary dependencies. They could be
Hi Alexander,
Great to hear fellow kiwis interested.
The dealing with artifacts is exactly the problem that resources were
designed to fix. A charm defines the resources it needs and as the charm
is deployed, it also has the resources fetched.
Personally I've not used any charms yet that
Hello everyone, I'm brand new to Juju, so first I'll say thanks for the exciting
project, I really think that Juju takes the right approach to deployment.
I will be using Juju to help software development companies build deployment
automation for their own work. The first requirements I'm
