extern/zrepl
1
0
Fork 0
mirror of https://github.com/zrepl/zrepl.git synced 2024-11-24 17:35:01 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: tutorial: minor typo + language fixes

Browse Source
This commit is contained in:
Christian Schwarz 2020-01-15 19:12:09 +01:00
parent 2927d0ca15
commit dd508280f0
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/tutorial.rst
View File

@ -52,9 +52,9 @@ Follow the :ref:`OS-specific installation instructions <installation>` and come
Generate TLS Certificates Generate TLS Certificates
------------------------- -------------------------
We use the `TLS client authentication transport <transport-tcp+tlsclientauth>` to protect our data on the wire. We use the :ref:`TLS client authentication transport <transport-tcp+tlsclientauth>` to protect our data on the wire.
To get things going quickly, we skip setting up a CA and generate two self-signed certificates as described :ref:`here <transport-tcp+tlsclientauth-2machineopenssl>`. To get things going quickly, we skip setting up a CA and generate two self-signed certificates as described :ref:`here <transport-tcp+tlsclientauth-2machineopenssl>`.
Again, for convenience, We generate the key pairs on our local machine and distribute them using ssh: For convenience, we generate the key pairs on our local machine and distribute them using ssh:
.. code-block:: bash .. code-block:: bash
:emphasize-lines: 6,13 :emphasize-lines: 6,13
@ -138,7 +138,7 @@ We define a corresponding **sink job** named ``sink`` in ``/etc/zrepl/zrepl.yml`
Apply Configuration Changes Apply Configuration Changes
--------------------------- ---------------------------
We use ``zrepl configcheck`` before to catch any configuration errors: no output indicates that everything is fine. We use ``zrepl configcheck`` to catch any configuration errors: no output indicates that everything is fine.
If that is the case, restart the zrepl daemon on **both** ``prod`` and ``backups`` using ``service zrepl restart`` or ``systemctl restart zrepl``. If that is the case, restart the zrepl daemon on **both** ``prod`` and ``backups`` using ``service zrepl restart`` or ``systemctl restart zrepl``.