Prepare for release v0.2.1

This commit is contained in:
2024-08-13 22:33:37 -04:00
parent 9cc4965ed8
commit a44bef1db9
6 changed files with 39 additions and 14 deletions
+1 -1
View File
@@ -5,7 +5,7 @@ For now, please manually install the binaries from the [latest release](https://
Additionally, MUTN is available as a source package ("[mutn](https://aur.archlinux.org/packages/mutn)") on the AUR.
Please note that the server binary must be called "libmuttonserver" in order for clients to successfully reach it.
Please note that the server binary (available in [libmutton releases](https://github.com/rwinkhart/libmutton/releases)) must be called "libmuttonserver" in order for clients to successfully reach it.
After placing the binaries in your $PATH, it is highly recommended to also download and correctly place/source the relevant [shell completions scripts](https://github.com/rwinkhart/MUTN/blob/main/wiki/completions.md).
+1 -1
View File
@@ -8,7 +8,7 @@ libmutton operates on a client-server model, and thus sync support requires you
For security reasons, libmutton deliberately does not support password-based SSH authentication; you must use key-based authentication to connect to your server (password-protected keys are also supported). You are responsible for setting up SSH connectivity on your own.
The libmutton server software is shipped as its own dedicated binary and must be installed on the server and configured with `libmuttonserver init`. The server binary _**MUST**_ be in your $PATH and _**MUST**_ be named "libmuttonserver" for clients to successfully reach it.
The libmutton server software is shipped as its own dedicated binary (in [libmutton releases](https://github.com/rwinkhart/libmutton/releases)) and must be installed on the server and configured with `libmuttonserver init`. The server binary _**MUST**_ be in your $PATH and _**MUST**_ be named "libmuttonserver" for clients to successfully reach it.
Once this has been done, you may proceed with the client setup:
1. Install MUTN