The file store

Noemata represents project content as files, including frame definitions, pages, queries, settings, and Markdown documents. The file store supports search and versioned changes. In fs.local, the project directory contains the deployment and draft. In fs.remote, ClickHouse stores the deployment; the draft can live in the store or on disk.

Editing project files

Edit project files in Noemata or with your usual file tools. Search and validate files before publishing them. When the project uses Git, review and revert disk changes with Git.

The things you work with are all files in a single store:

• Frames — frame definitions, stored in *.frame.json files
• Pages and blocks — stored in a frame definition or in *.templates.json files
• Markdown — notes, investigations, runbooks, post-mortems, technical documentation, and everything else that fits in a Markdown file.

Storage and conflicts

A project’s deployment is stored on local disk or in a file store in ClickHouse, and its drafts are on disk or in the store. When a checkout and the deployment both change a file, the conflict has to be resolved. The Workspace section covers conflicts, multi-project layout, ownership, and what git tracks:

• Projects — one project per directory, or several
• Storage modes — fs.local / fs.remote
• Publishing & fetching — moving content between disk and the store by hand
• Resolving conflicts — what happens when disk and the store disagree
• Ownership & version control — managed vs. user-owned content, what’s gitignored