diff options
| author | James Ennis <james.ennis@codethink.com> | 2018-10-26 12:14:58 +0100 |
|---|---|---|
| committer | James Ennis <james.ennis@codethink.com> | 2018-10-26 12:14:58 +0100 |
| commit | 20e5c58ac19b2e971634d3803bfc5ff271c760ce (patch) | |
| tree | 36af9d8242d9ceba5108e39a36909eb89a353da2 | |
| parent | e4c18ba4dc82f89bb22669d15334275ac9692623 (diff) | |
| download | buildstream-20e5c58ac19b2e971634d3803bfc5ff271c760ce.tar.gz | |
using_configuring_artifact_server.rst: Fix lines that are too long
| -rw-r--r-- | doc/source/using_configuring_artifact_server.rst | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/source/using_configuring_artifact_server.rst b/doc/source/using_configuring_artifact_server.rst index 813952cb3..117d8e544 100644 --- a/doc/source/using_configuring_artifact_server.rst +++ b/doc/source/using_configuring_artifact_server.rst @@ -155,9 +155,12 @@ Instance with push and requiring client authentication: Managing the cache with systemd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -It is better to run the cache as a systemd service, especially if it is running on a dedicated server, as this will allow systemd to manage the cache, incase the server ever encounters any issues. +It is better to run the cache as a systemd service, especially if it is running +on a dedicated server, as this will allow systemd to manage the cache, in case +the server encounters any issues. -Below are two examples of how to run the cache server as a systemd service, one is for pull only and the other is configured for push & pull. +Below are two examples of how to run the cache server as a systemd service, one +is for pull only and the other is configured for push & pull. .. code:: ini @@ -193,7 +196,10 @@ Below are two examples of how to run the cache server as a systemd service, one [Install] WantedBy=multi-user.target -Here we define when systemd should start the service, which is after the networking stack has been started, we then define how to run the cache with the desired configuration, under the artifacts user. The {{ }} are there to denote where you should change these files to point to your desired locations. +Here we define when systemd should start the service, which is after the networking +stack has been started, we then define how to run the cache with the desired +configuration, under the artifacts user. The {{ }} are there to denote where you +should change these files to point to your desired locations. For more information on systemd services see: `Creating Systemd Service Files <https://www.devdungeon.com/content/creating-systemd-service-files>`_. |