Fix documentation for enabling lorax-composer.socket

It needs to be enabled AND started for it to work.
This commit is contained in:
Brian C. Lane 2018-05-14 14:09:46 -07:00
parent 55b89d1aeb
commit 1fef566bb2

View File

@ -19,9 +19,10 @@ Installation
The best way to install ``lorax-composer`` is to use ``sudo dnf install The best way to install ``lorax-composer`` is to use ``sudo dnf install
lorax-composer composer-cli``, this will setup the weldr user and install the lorax-composer composer-cli``, this will setup the weldr user and install the
systemd socket activation service. You will then need to enable it with ``sudo systemd socket activation service. You will then need to enable it with ``sudo
systemctl enable lorax-composer.socket``. This will leave the server off until systemctl enable lorax-composer.socket && sudo systemctl start
the first request is made. Systemd will then launch the server and it will lorax-composer.socket``. This will leave the server off until the first request
remain running until the system is rebooted. is made. Systemd will then launch the server and it will remain running until
the system is rebooted.
Quickstart Quickstart
---------- ----------
@ -29,8 +30,9 @@ Quickstart
1. Create a ``weldr`` user and group by running ``useradd weldr`` 1. Create a ``weldr`` user and group by running ``useradd weldr``
2. Remove any pre-existing socket directory with ``rm -rf /run/weldr/`` 2. Remove any pre-existing socket directory with ``rm -rf /run/weldr/``
A new directory with correct permissions will be created the first time the server runs. A new directory with correct permissions will be created the first time the server runs.
3. Enable the socket activation with ``systemctl enable lorax-composer.socket`` or 3. Enable the socket activation with ``systemctl enable lorax-composer.socket
run it directly with ``lorax-composer /path/to/blueprints/`` && sudo systemctl start lorax-composer.socket`` or run it directly with
``lorax-composer /path/to/blueprints/``
The ``/path/to/blueprints/`` directory is where the blueprints' git repo will The ``/path/to/blueprints/`` directory is where the blueprints' git repo will
be created, and all the blueprints created with the ``/api/v0/blueprints/new`` be created, and all the blueprints created with the ``/api/v0/blueprints/new``