Deploying local code

[Mark Shuttleworth]

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
>    or similar, providing a fast proxy with proper control over
>    what's delivered.

The general idea is that your charm can inspect its environment and then
request the relevant resources. Tarballs would suffice in most cases to
aggregate dependencies.

Charms must be architecture-neutral, the resources can be specific to
particular architectures.

You can of course also setup a local service as you describe, with HTTP
access to content, but the main issue you'll run into is punching
through firewalls when your charms are used around the world.

Mark