You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Valentin Lab f14046610e new: [letsencrypt] support for scheduling relation. 6 years ago
apache chg: dev: whitespaces !minor 6 years ago
bitwarden new: [bitwarden] new charm. 6 years ago
cron new: [cron] new charm 6 years ago
docker-host new: [docker-host] new charm. 8 years ago
letsencrypt new: [letsencrypt] support for scheduling relation. 6 years ago
mattermost new: [mattermost] new charm 6 years ago
mysql new: dev: [postgres,mysql] moved out of 'precise' subdirectory. !minor 9 years ago
odoo-tecnativa chg: dev: whitespaces !minor 6 years ago
postgres chg: postgres 11 is not fully compatible with odoo 12 6 years ago
postgres-alpine new: ``charm`` and ``service`` are now clear distinct concept 6 years ago
precise chg: dev: whitespaces !minor 6 years ago
radicale new: added ``radicale``. 7 years ago
rancher new: [rancher] new minimal charm. 7 years ago
rancher-agent new: [rancher-agent] new charm for rancher agent. 7 years ago
rsync-backup-target chg: [rsync-backup-target/build] added ``-H`` in accepted options on server side. 8 years ago
sftp new: ``charm`` and ``service`` are now clear distinct concept 6 years ago
softether new: [softether] new charm. 8 years ago
traefik new: ``charm`` and ``service`` are now clear distinct concept 6 years ago
whoami new: [traefik,whoami] new charms 6 years ago
README.rst new: doc: added quick ``README.rst`` to detail purpose and related packages. 10 years ago

README.rst

0k-charms
=========

This package provides charms for the ``lxc-deploy`` and
``docker-build-charm`` commands respectively from ``lxc-scripts`` and
``0k-docker`` packages.

A charm is basically a set of metadata and a shell script that will be
executed to create an image for lxc or docker.


Installation
============

Be sure to install ``lxc-scripts`` and ``0k-docker`` packages and that
their binaries are accessible to user 'root'.

By default, ``lxc-deploy`` and ``docker-build-charm`` will look for the
charm store to be located in ``/srv/charm-store``. This can be a symbolic
link.

For instance, if ``0k-charms`` is installed in ``/opt/apps/0k-charms``,
you would do::

ln -sf /opt/apps/0k-charms/precise /srv/charm-store