Mindex

Git

Commit, push and browse history without leaving the app. It is ordinary Git on an ordinary repository.

A vault is a folder, so it can be a Git repository. Mindex has Git built in: stage, commit, push, pull and read the log from inside the app.

Nothing about it is special. The repository is a normal one — clone it, run git log in a terminal, open it in any Git client. Mindex is a front end, not a format.

Why Git rather than sync

There is no Mindex cloud. Git is the recommended way to move a vault between machines, and it brings a history someone else can read as a side effect.

Because the vault is ordinary files, any sync tool you already trust works too. Git is simply the one that also answers "what changed, and why".

Getting started

A folder that is not a repository can be initialised from inside Mindex, when you ask it to. See Commit and push for connecting a remote.

What to commit

All of it, including .mindex/types/ and the per-folder context files — those are part of the vault, not of the installation. .mindex/cache.json and .mindex/tmp/ are derived and can be ignored.

Git and local history are different things

Git records what you chose to commit. Local history records every write, whether you meant it or not. They answer different questions and neither replaces the other.