I want to discuss how the implementation of these “hooks only” charms could be made more “typical” and “best practice” to good charming.
The challenge is to keep it extremely minimal to assist in the learning process. Possibly leading into the reactive framework further down, but not to the expense of adding too much complexity.
I would like to fire off a discussion around how to actually implement the hooks to be:
Minimal
Best practice or at least typical.
“Just enough” introduction to other concepts outside of “hooks”. Hook contexts, configuration validation, juju eventloop etc.
Ideally, making the code also “OS agnostic” - not relying on Ubuntu to get juju basic concepts going.
Thanks for your great tutorial and detailed explaination, which is really helpful! There are some minor suggestions regarding your tutorial in GitHub link.
a. In the part Remove the application
The following command causes an error as ‘Unrecognized command’
$ juju remove application tiny-python
It might be like this:
$ juju remove-application tiny-python
b. In the part Modifying the ‘install’ hook
Before modifying Install script, is it necessary to specify the exact path of install? like ~/tiny_python/hooks/install .
(There is a tree above demonstrating the path though :D)
