juju-core

Merge lp:~lazypower/juju-core/docs into lp:juju-core/docs

  1. docs
  2. Merge into docs
Proposed by Charles Butler
Status: Merged
Merged at revision: 215
Proposed branch: lp:~lazypower/juju-core/docs
Merge into: lp:juju-core/docs
Diff against target: 12 lines (+1/-1)
1 file modified
htmldocs/authors-charm-components.html (+1/-1)
To merge this branch: bzr merge lp:~lazypower/juju-core/docs
Reviewer Review Type Date Requested Status
Marco Ceppi (community) Approve
Review via email: mp+201790@code.launchpad.net

Commit message

added Charm Hooks link to Charm Components documentation

To post a comment you must log in.
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

LGTM +1

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'htmldocs/authors-charm-components.html'
2--- htmldocs/authors-charm-components.html 2013-12-16 14:54:13 +0000
3+++ htmldocs/authors-charm-components.html 2014-01-15 14:50:12 +0000
4@@ -88,7 +88,7 @@
5 <ul>
6 <li><code>/hooks</code> must be a directory holding
7 executables with specific names, that will be invoked by juju at the relevant times.
8- A charm needs to implement at least one hook in order to do anything at all. How to implement hooks is covered more thoroughly in the <a href="">Hooks section</a></li>
9+ A charm needs to implement at least one hook in order to do anything at all. How to implement hooks is covered more thoroughly in the <a href="./authors-charm-hooks.html">Hooks section</a></li>
10 <li><code>config.yaml</code> defines service configuration options.<a href="./authors-charm-config.html">
11 The config.yaml file is descibed more fully here</a>.</li>
12 <li><code>icon.svg</code> is used to identify your charm in the GUI and in the charm store.<a href="authors-charm-icon.html">See the walkthrough for creating an icon.</a></li>

Subscribers

People subscribed via source and target branches