Orichalcum File Helper - Homepage

Summary

Orichalcum is a tool that helps manage files. The core philosophy behind Orichalcum is to let the user retain control over what Orichalcum does, it facilitates operations but doesn't enable or require a hands-off workflow that forces out the awareness of manually organizing something: it's minimally aggressive automation.

Features

Orichalcum only partially adheres to the unix philosophy, doing one thing (managing files) but giving you several discreet tools which, while they work together and depend on eachother, aren't all fundamentally doing the same thing. The main features of Orichalcum are as follows:

File tracking

At its core Orichalcum tracks files: their names, their locations within the directory, their hashsums, the time they were added to the repo, the last time they were modified. In this respect, Orichalcum can (and effectively does) function as an OS-agnostic* file system record. Personally I've always had lots of use for the date modified/date created of a file, but I've always found it a little unsettling to trust the system to keep consistent information, especially when I move a working file over several machines running different OSs and file systems.

Automatic Archives

Perhaps the most useful and straight-forward feature is the ability to create local snapshots of files. These can be automated to time intervals or size change intervals, but regardless can be manually created whenever.

Repo Syncing

Another major motivation for the design and execution of Orichalcum is to create a system that encapsulates groups of files into solid units which can be carried around from file system to file system conveniently and reliably. This encapsulation allows Orichalcum to backup the repository as a whole, and synchronize multiple copies of the repository.

File Resiliance

While file corruption is not an everyday thing, and there already exists far better error-correction that what is proposed here, Orichalcum comes with a RED feature, which allows us to store a redundant version of the file. This is made possible by the goofily-great RED Copy library, which is suitable only for the most paranoid of users.