mxmehl/mehl.mx
1
0
Fork 0
Code Issues 3 Pull Requests Actions Releases Wiki Activity

Compare commits

base: mxmehl:main
Branches Tags
mxmehl:main
..
compare: mxmehl:f810cf068670e42714fc3795ae75fb1f01fabae8
Branches Tags
mxmehl:main

7 Commits
main ... f810cf0686

Author SHA1 Message Date
Max Mehl
f810cf0686 fix link
All checks were successful
Website build and deploy / build (pull_request) Successful in 39s
Details
2026-04-01 11:43:00 +02:00
Max Mehl
0b1d9b0c4d test: other way
Some checks failed
Website build and deploy / build (pull_request) Failing after 37s
Details
2026-04-01 11:41:09 +02:00
Max Mehl
563de8b538 test: alternative 2
Some checks failed
Website build and deploy / build (pull_request) Failing after 41s
Details
2026-04-01 11:38:31 +02:00
Max Mehl
4b34706b40 test: alternative 1 2026-04-01 11:36:50 +02:00
Max Mehl
d11b632801 test: doesn't run?
Some checks failed
Website build and deploy / build (pull_request) Failing after 40s
Details
2026-04-01 11:35:12 +02:00
Max Mehl
da9938c90d test: broken link 2026-04-01 11:34:11 +02:00
Max Mehl
3a5b758b10 fix: broken links, add check to CI 2026-04-01 11:31:35 +02:00
2 changed files with 6 additions and 8 deletions
Expand all files Collapse all files

12
content/blog/2023-09-seafile-mirror.md
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://github.com/mxmehl/seafile-mirror). location: [**Seafile Mirror**](https://src.mehl.mx/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://github.com/mxmehl/seafile-mirror) takes care of all [seafile-mirror](https://src.mehl.mx/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://github.com/mxmehl/seafile-mirror/issues/2)) ([#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))
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

2
content/blog/2026-03-gnulinux-podcast-lieferketten-deutsche-bahn/index.md
View File

@@ -8,7 +8,6 @@ tags:
- Community - Community
- DeutscheBahn - DeutscheBahn
- SupplyChain - SupplyChain
summary: 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 und der FOSDEM, in denen ich über die Herausforderungen und Chancen von Software-Lieferketten bei der DB gesprochen habe.
headerimage: headerimage:
src: ciw.jpg src: ciw.jpg
alt: The famous "Captain it's Wednesday" comic alt: The famous "Captain it's Wednesday" comic
@@ -18,7 +17,6 @@ audio: https://gnulinux.ch/podcast/CIW175.mp3
event: event:
name: Captain it's Wednesday Podcast name: Captain it's Wednesday Podcast
href: https://gnulinux.ch/ciw175-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. 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.