I ran across a case where a charm needs to deploy a local repository for it's (proprietary) binaries to be installed. It currently instructs users to install apache and setup a repo on machine 0, which is a workable solution but not very user friendly.
I thought it would be nice if the ubuntu-repository-cache charm could facilitate the hosting of a private repository. The new reactive/compose functionality[1] should be landing in charm-helpers soon, and it's layered approach to charm development seems like a good fit here: a base layer that encapsulates all of the fundamental bits of running a repository, with a layer on top that adds the current functionality for running an ubuntu mirror. It would allow partners who want to host a private repository to take advantage of the awesome work done in the current ubuntu-repository-cache charm.
I ran across a case where a charm needs to deploy a local repository for it's (proprietary) binaries to be installed. It currently instructs users to install apache and setup a repo on machine 0, which is a workable solution but not very user friendly.
I thought it would be nice if the ubuntu- repository- cache charm could facilitate the hosting of a private repository. The new reactive/compose functionality[1] should be landing in charm-helpers soon, and it's layered approach to charm development seems like a good fit here: a base layer that encapsulates all of the fundamental bits of running a repository, with a layer on top that adds the current functionality for running an ubuntu mirror. It would allow partners who want to host a private repository to take advantage of the awesome work done in the current ubuntu- repository- cache charm.
[1] http:// charmsreactive. readthedocs. org/en/ latest/