Skip to Content

What is kept where

Every file and key zekno keeps, on your machine and on the server.

Pre-alpha and unaudited

The command-line tool, the runner and the core library have had internal reviews only. Do not use them for anything you could not afford to lose, and do not rely on them in production before an external audit.

On your machine:

WhatWhere
Your signing key and the team codeThe system keychain, service app.zekno.cli. Never in a file; there is no option for that.
Team lists, connected servers~/.zekno/profile.json (or ZEKNO_HOME). Public keys and signatures only.
Secrets~/.zekno/secrets/<server id>/<app>.json, as encrypted, signed records. A value cannot be shown again after it is set.
Deploy history~/.zekno/history/<server id>/<app>.json: the last 50 signed deploys of each app, for rollback.
What the server holds~/.zekno/held/<server id>/<app>.json: the secret statements and versions the server reported to the last deploy of each app in the new deploy format. A statement says a secret's name, its version, the hash of its sealed value and who set it, never a value. zekno secret set and rm read it, offline, for the next version.
Project files used here~/.zekno/links.json: the real path and SHA-256 of each zekno.json used on your machine, at most 500.
A runner on your machine~/.zekno/runner/<name>, unless --home named another folder.
Which app a folder deployszekno.json in the project folder.
An app's settingszekno.app.json in the project folder, beside the code. It names secrets but never holds a value, so it is safe to commit.

The profile folder has mode 700 and its files mode 600. App state and logs are never stored.

Changing a setting, with zekno settings set, unset or init or on the settings screen, writes zekno.app.json and nothing else, and contacts no server. The change runs after the next deploy, whose signed text is in the deploy history like any other. zekno add writes zekno.app.json and stores the app's new secrets, and contacts no server. A Compose file written by hand is never written: only the secrets are stored.

The file you give zekno secret import is read once and never copied: its values are kept only as the encrypted records above. zekno doctor itself writes nothing, on your machine or on a server. SSH keeps its own records: it may add the server to known_hosts on your machine, and the server logs the login.

The files in ~/.zekno are safe to read but are not believed as they stand. Every command rebuilds the team from the signed team lists, starting from the team code in the keychain, and checks each secret and each history entry against it. A file changed by something other than zekno is refused or ignored, never signed. The folder holds no command to run.

What the server holds is written by a deploy in the new deploy format, right after it reads the server, and is replaced whole each time; nothing else writes it. A file that cannot be read counts as empty. It can only raise the next version of a secret: it never gives a value, and never decides what a deploy lists.

On the server, including the secret records it keeps, see the runner page.