Compare commits

...

4 Commits

Author SHA1 Message Date
6fc22a7a7f fix: seafile-mirror git link
All checks were successful
Website build and deploy / build (push) Successful in 55s
2026-04-24 10:55:09 +02:00
de0c9f5e01 feat: add mastodon link
All checks were successful
Website build and deploy / build (push) Successful in 50s
2026-04-01 11:51:11 +02:00
c9d37811aa chore: shorten summary for podcast
All checks were successful
Website build and deploy / build (push) Successful in 53s
2026-04-01 11:49:20 +02:00
83b7c5f3bd Merge pull request 'Fix broken links, add linkcheck to CI' (#16) from fix-links into main
All checks were successful
Website build and deploy / build (push) Successful in 51s
Reviewed-on: #16
2026-04-01 11:45:58 +02:00
2 changed files with 8 additions and 6 deletions

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,
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
location: [**Seafile Mirror**](https://src.mehl.mx/mxmehl/seafile-mirror).
location: [**Seafile Mirror**](https://github.com/mxmehl/seafile-mirror).
## My requirements
@@ -64,7 +64,7 @@ turned out that this tool has a number of fundamental issues:
## 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:
* 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.
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
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).
([#2](https://src.mehl.mx/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))
([#2](https://github.com/mxmehl/seafile-mirror/issues/2))
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

View File

@@ -8,6 +8,7 @@ tags:
- Community
- DeutscheBahn
- SupplyChain
summary: Ich wurde mal wieder von Ralf Hersel zum “Captain its Wednesday” Podcast von GNU/Linux.ch eingeladen, um über Software-Lieferketten bei der Deutschen Bahn zu sprechen. Anlass waren meine jüngsten Vorträge auf der FOSS Backstage und der FOSDEM, in denen ich über die Herausforderungen und Chancen von Software-Lieferketten bei der DB gesprochen habe.
headerimage:
src: ciw.jpg
alt: The famous "Captain it's Wednesday" comic
@@ -17,6 +18,7 @@ audio: https://gnulinux.ch/podcast/CIW175.mp3
event:
name: Captain it's Wednesday Podcast
href: https://gnulinux.ch/ciw175-podcast
mastodon_toot_url: https://mastodon.social/@mxmehl/116318946107759692
---
Ich wurde mal wieder von Ralf Hersel zum "Captain it's Wednesday" Podcast von GNU/Linux.ch eingeladen, um über Software-Lieferketten bei der Deutschen Bahn zu sprechen. Anlass waren meine jüngsten Vorträge auf der [FOSS Backstage](/blog/2026-03-foss-backstage-getting-real-supply-chain) und der [FOSDEM](/blog/2026-01-fosdem-supply-chain-strategy), in denen ich über die Herausforderungen und Chancen von Software-Lieferketten bei der DB gesprochen habe.