casync VS datacurator-filetree

For arbitrary state changes however, it's better to use something like casync. Note that there are a lot of tunables, implicit and explicit; for package indexing I would particularly think about "how is the index sorted" and "what is the desired chunk size".

If you just want something practical to play with, see casync. Even if it doesn't fit your workflow, or if you think you can do better, chances are you're best off building on top of it or adding patches to it, not starting from scratch.

You probably want casync.

Obligatory link to casync, which implements this better than most alternatives.

(personally, I think more people need to be aware of casync for the update storage/distribution problem. It isn't perfect for every use case, but it's good enough that you're probably better off wrapping/forking it rather than reimplementing it badly from scratch)

Does something like casync (https://github.com/systemd/casync or https://github.com/folbricht/desync) serve any purpose or provide any advantage to propagating rpm changes over rsync?

Software that comes to mind for syncing lots of small files: git (and other source versioning tools), casync (https://github.com/systemd/casync) and a go implementation (https://github.com/folbricht/desync). Not really an answer and I can't think of a way to shoehorn that into your workflow, but maybe it leads you down a useful road.

Casync – A Content-Addressable Data Synchronization Tool\ (15 comments)

For the most part I follow this file tree. However when it comes to some of my intererests, like electronics, I am unsure if I should keep splitting these interest-based files by file type, for example:

I have redesigned my entire computer to follow the datacurator methodology: https://github.com/roboyoshi/datacurator-filetree/tree/main/root

P.S. I've been lurking this sub and have considered this particular problem for a long time and have read maybe everything Karl, Nayuki, Reddit, and Hacker News have had to say on the subject. Running into this post is a treat. If tags don't work out for you roboyoshi and contributors have made a really nice unified file tree https://github.com/roboyoshi/datacurator-filetree

As always, credit to u/Roboyoshi for the Datacurator filetree.

But it will obviously depend on the use case. As example you have JohnnyDecimal or a more simple approach

This tool will be useful to generate repos like these and sharing them with friends without actually needing to share them TB of data.

back in the days I started with this structure tho: https://github.com/roboyoshi/datacurator-filetree

This is a mix of this post and https://github.com/roboyoshi/datacurator-filetree. Im still having trouble with a few things: