OSSForks/opsschool-curriculum
1
0
Fork 0
mirror of https://github.com/opsschool/curriculum.git synced 2026-01-15 12:15:03 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated todos.

Browse Source
This commit is contained in:
Stas SUȘCOV
2012-11-23 19:13:53 +02:00
parent 23bf6bb6a8
commit c89d598f8e
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
config_management.rst
View File

@@ -224,11 +224,13 @@ directory layout we will use in our example will look like this: ::
| `-- init.sls
`-- top.sls
.. todo:: The following paragraph needs some further explanation.
When creating new states, there is a file naming convention.
Look at ``init.sls``, it is the default filename to be searched when loading
a state. This reminds of modules in Python or default web page name
``index.html``.
``init.sls`` is the default filename to avoid directory filename in ``top.sls``,
reminds of modules in Python or default web page name ``index.html``. This file
will also contain our snippet from above.
So when you create a new directory for a state with ``init.sls`` you do not write
``pkg: new_state.init``, use just ``pkg: new_state.init``.
Now to deploy it, we will use the function ``state.sls`` and indicate the state
name:
@@ -278,7 +280,8 @@ Let's add a new virtual host to our server now using the ``file`` state. We
can do this by creating a separate state file or re-using the existing one.
Since creating a new file will keep code better organised, we will take that approach.
.. todo:: explain which file this content will be in
We will create a new ``sls`` file with a relevant name, say ``www_opsschool_org.sls``
with the content from below:
.. code-block:: yaml