Hi. I definitely need to update the website.
The design for Bazil ran into a funky edge case with version vectors
vs whole-subtree renames that I never gathered sufficient motivation
to think hard enough about to figure out an answer. It's complex
enough that I think the only reasonable next step would be to start
formally proving the sync algorithm.
Instead, I'm using
https://github.com/bazil/plop all the time. I
haven't taken the time to document it sufficiently.. It's a much
simpler[1] immutable fixed-content store on top of S3-style object
stores, and avoids bazil's problem by delegating sync to git. As far
as git is concerned, it's just a bunch of symlinks, and any machine
with the right config, secrets, a clone of the git repo, and `plop
mount` running has seamless access to all the data added.
Looks like this:
```
$ date >myfile
$ plop add myfile
$ ls -l myfile
lrwxrwxrwx 1 tv tv 70 Mar 4 16:37 myfile ->
/media/plop/demovolume/gzgoozwihdeqo851tcyqwntn9hdigh5h7gguchd5njkazbfwgqro
$ git add myfile
$ git commit -m 'blah blah'
```
[1]: Well, plop's crypto use is actually more advanced. If bazil
itself continues making progress one day, I'll port it to use plop as
a library.
https://github.com/bazil/plop/blob/main/doc/crypto.dot
> --
> You received this message because you are subscribed to the Google Groups "Bazil File System development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
bazil-dev+...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/bazil-dev/b67f9344400cbe81434f616f0e98aa61.lykso%40lyk.so.