fix: seafile-mirror git link
All checks were successful
Website build and deploy / build (push) Successful in 55s

This commit is contained in:
2026-04-24 10:55:09 +02:00
parent de0c9f5e01
commit 6fc22a7a7f

View File

@@ -20,7 +20,7 @@ all its files isn't so trivial. This is because the files are stored in a layout
similar to bare Git repositories, and Seafile's headless tool, seafile-cli, similar to bare Git repositories, and Seafile's headless tool, seafile-cli,
is... suboptimal. So I created what started out as a wrapper for it and ended up is... suboptimal. So I created what started out as a wrapper for it and ended up
as a full-blown tool for automatically synchronising your libraries to a backup as a full-blown tool for automatically synchronising your libraries to a backup
location: [**Seafile Mirror**](https://src.mehl.mx/mxmehl/seafile-mirror). location: [**Seafile Mirror**](https://github.com/mxmehl/seafile-mirror).
## My requirements ## My requirements
@@ -64,7 +64,7 @@ turned out that this tool has a number of fundamental issues:
## The solution ## The solution
[seafile-mirror](https://src.mehl.mx/mxmehl/seafile-mirror) takes care of all [seafile-mirror](https://github.com/mxmehl/seafile-mirror) takes care of all
these stumbling blocks: these stumbling blocks:
* It downloads/syncs defined libraries in customisable intervals * It downloads/syncs defined libraries in customisable intervals
@@ -95,13 +95,13 @@ and configuration.
The tool has been running every day since a couple of months without any issues. The tool has been running every day since a couple of months without any issues.
However, I could imagine a few more features to be helpful for more people: However, I could imagine a few more features to be helpful for more people:
* Support of encrypted libraries: Shouldn't be a big issue, it would require
passing the password to the underlying seafile-cli command.
([#1](https://github.com/mxmehl/seafile-mirror/issues/1))
* Support of login tokens: Currently, only user/password auth is supported which * Support of login tokens: Currently, only user/password auth is supported which
is fine for my use-case as it's just a read-only user. This wouldn't be hard is fine for my use-case as it's just a read-only user. This wouldn't be hard
to fix either, seafile-cli supports it (at least in theory). to fix either, seafile-cli supports it (at least in theory).
([#2](https://src.mehl.mx/mxmehl/seafile-mirror/issues/2)) ([#2](https://github.com/mxmehl/seafile-mirror/issues/2))
* Support of encrypted libraries: Shouldn't be a big issue, it would require
passing the password to the underlying seafile-cli command.
([#3](https://src.mehl.mx/mxmehl/seafile-mirror/issues/3))
If you have encountered problems or would like to point out the need for If you have encountered problems or would like to point out the need for
specific features, please feel free to contact me or comment on the Mastodon specific features, please feel free to contact me or comment on the Mastodon