Greetings
In accordance with our unmaintained charm workflow
https://juju.ubuntu.com/docs/charm-unmaintained-process.html we have 2
items that have expired the maintainer-needed requirement.
https://bugs.launchpad.net/charms/+source/buildbot-slave/+bug/1028192
Hi everyone,
Please consider this my application to join the Charmers team!
I've been working in the Juju ecosystem for about 7 months, writing and
reviewing charms, contributing to charm-related tools and libraries, and
establishing automated-testing for charms and bundles. Here's a
Does juju team already have knowledge how the best split hooks and
templates to provide support for different OS. AS i google somebody
already have patches to deploy into centos. For example now - i want
to rewrite wordpress charm to support debian wheezy.
--
Vasiliy Tolstov,
e-mail:
There shouldn't be much in the WordPress charm that's Ubuntu specific and
should work fine on Debian. Some charms already have logic to support
multiple Ubuntu releases by either coding switches in the hooks or by
leveraging a configuration management tool like chef or puppet which
abstracts that.
TL;DR: It has been surprisingly difficult As per what has already been done
for the units and services collections, we will continue with the approach
of using uuid:id style string ids while also adding separate env-UUID
and collection specific identifier fields.
Jesse and I have been making the
