@thumper
Following the last link I’ve modify the files inside the hooks directory (install, start, stop and config-changed) and result of its build is that
$:charm build layer-lab --force
build: DEPRECATED: INTERFACE_PATH environment variable; please use CHARM_INTERFACES_DIR instead
build: DEPRECATED: LAYER_PATH environment variable; please use CHARM_LAYERS_DIR instead
build: Please add a `repo` key to your layer.yaml, with a url from which your layer can be cloned.
build: Destination charm directory: /home/richardsith/charms/builds/ngnix-lab
build: Processing layer: layer:options
build: Processing layer: layer:basic
build: Processing layer: ngnix-lab (from ngnix-lab)
proof: I: `display-name` not provided, add for custom naming in the UI
proof: W: Includes template README.ex file
proof: W: README.ex includes boilerplate: Step by step instructions on using the charm:
proof: W: README.ex includes boilerplate: You can then browse to http://ip-address to configure the service.
proof: W: README.ex includes boilerplate: - Upstream mailing list or contact information
proof: W: README.ex includes boilerplate: - Feel free to add things if it's useful for users
and run the deploy, now its JUJU status is:
$:juju status
Model Controller Cloud/Region Version SLA Timestamp
juju-dev maas-cloud-controller maas-cloud/default 2.7.3 unsupported 20:38:39Z
App Version Status Scale Charm Store Rev OS Notes
layer-lab active 1 layer-lab local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
layer-lab/0* active idle 0 10.0.0.19 Started with message:
Machine State DNS Inst id Series AZ Message
0 started 10.0.0.19 juju-dev bionic juju-dev Deployed
in JUJU gui
but I’m not sure.