The curator is a meta-data repository that organizes your files. Designed to utilize modern filesystems to their full potential while keeping the operator in total control
- Makes no assumptions about nor places any demands on your workflow(s)
- Fault tolerant design that leverages OS guarantees for graceful degredation in the case of user error
- Configure for what you want, not what to do. Write 100 lines of config, it reorganizes 100K files
- Demands your workflow adapt to its assumptions, behaves unexpectedly if violated
- Usually single point of failure, degrades terribly if corrupted
- Narrow purpose restricts the amount of compatible workflows, frequently involving repetitive list sifting
Rest assured the curator doesn't do anything risky or evil with your data
- No vendor lock in! Delete the curator's DB at no risk to your directory trees or your stored meta-data
- No propritary meta-data files. All meta-data are expressed as directory trees or attached via NTFS streams or xattrs. Access them directly via
notepad
andcli
commands, respectively - No networking capabilities, the curator respects your privacy.
- It uses Unix domain sockets that are literally incapable of connecting to another machines
- For networked clients that need to access meta-data, attributes used by the curator are fully compatible with both Windows SMB and Samba (with some config)
- No data loss risk in the repository. Curator will never run the equivlent of
rm -rf
and or overwrite files. In fact, to regenerate a directory tree, you must delete it yourself (or the command fails)
- 100% native program written in C 20 with the resource efficiency you'd expect
- Easy to understand & write ini configurations
- Monitors multiple paths for directories & files to injest
- Incrementally dedupe files as they are added
- Murmur3 hash based binary level deduplication
- PHash perceptual deduplication for images
- Integrated FFMPEG thumbnailer for images & videos
- Groups "related" files and maintain file ordering
- Regex based renaming capabilities (with named capture groups)
- Transform files by invoking other programs (un-archiving, re-encoding, etc)
- Rules based directory tree generation
- Hard links support to keep file contents synced & reduce duplication
See the configuration manual for how it works