NOTE: Lodestone is a Work-in-Progress and is not production ready.

Lodestone is designed to be the modern and digital equivalent of a home filing cabinet. If you've gone searching for something similar in the past, you might be familiar with terms like Electronic Document Management System (EDMS), Document Management System (DMS) or Personal Archival.

Lodestone is designed around a handful of core features:

• Full text document search - It doesn't matter what format you're document is in, we should be able to parse it (using OCR) and let you search for the text.
• Rich tagging - Unlike a physical file cabinet where a document can only exist in one place, digital documents support tags, allowing you to create a flexible organizational structure that works for you.
• Automated - Document collection & OCR processing should be automatic. Just saving a file to your network drive should be enough to start document processing.
• Non-destructive - When Lodestone processes a document, the original file will be left untouched, exactly where you left it.
• Web Accessible - Lodestone is designed to run on a trusted home server and be accessible 24x7.
• Filesystem/Cloud Sync - Optionally synchronize your tagged documents via a cloud storage provider of your choice (Dropbox, GDrive, etc) or access via a FUSE filesystem mount.

More screenshots available in the docs/screenshots directory.

Lodestone is made up of a handful of open-source components, and as such its easiest to deploy using Docker/Docker Compose

docker-compose up

# then open the following url in your browser

http://localhost/

Place your documents in the /data/storage/documents directory, and the Filesystem Collector should automatically start processing them.

If you would like some test documents to play with safely, you can take a look at the LodestoneHQ/lodestone-test-docs repository.

Lodestone follows a Convention over Configuration design, which means that it works out of the box with sane defaults, but you can customize them to match your needs.

Most of the configuration files are stored in the webapp image (source code here), and requested by various components when they start up.

• filetypes.json (backend/data/filetypes.json) contains lists of includes and excludes that are used by the processor container to decide which files to process and load into the database.

• tags.json (backend/data/tags.json) contains a nested structure of labels that can be used to group tags and seach for your documents in the Lodestone web UI.

• mapping.json (backend/data/mappings.json) is used to ensure that the elasticsearch container has a consistent data storage structue.

To overide these files, just setup a Docker volume binding to the specified file in the /lodestone/data/ directory in the webapp container.

Lodestone is a very opinionated solution for personal document management. As such, there's a couple things you should know before even considering it.

• Currently there's no user management. Lodestone is designed to run at home, on your trusted network. This may be reconsidered at a future date.

• Limited support for file types

  • doc,docx,xls,xlsx, ppt, pptx - Microsoft Office Documents

  • pages, numbers, key - Apple iWork Documents

  • pdf

  • rtf

  • jpg, jpeg, png, tiff, tif

    If you think there are additional document types that may be useful to support, please open an issue.

As mentioned above, Lodestone isn't some magical new technology. EDMS and DMS systems have been around for a long time, but unfortunately they all seem to miss one or more features that I think are required for a modern filing cabinet.

Here's some of my research, but you should take a look at them yourselves.

Place your documents in the /data/storage/documents directory, and the Filesystem Collector should automatically start processing them.

If you would like some test documents to play with safely, you can take a look at the LodesoneHQ/lodestone-test-docs repository.

If the processor doesn't pick up your files, you may have to fake an update to them to change the timestamp. This is temporary and will be resolved in a future release. You can use the command below to update the timestamp and trigger the processor:

find . -exec touch {} \;

Please see our Issues system for a list of items that have been reported. All issues for the project are contained in this repo. Issues are labeled by area affected, status, and other labels as appropriate. Below are some example of filtering issues by label:

• Issues in Progress
• UI Issues
• Processor Issues
• Documentation Needs

Please feel free to create an issue if you have an idea for a new feature, find a bug, or have a question.

• rock by Dobs from the Noun Project