Everlock 0.6.1
The 0.6.1 release finishes what 0.6.0 started. Administration now has a third outlet — a plain HTTP API with an OpenAPI document and a Swagger UI — generated from the same command registry as the SSH
Documentation
Tag: admin
Admin over HTTP
The `backend-admin-http` outlet serves two surfaces on its pinned vhost: the web dashboard at `/admin` and the HTTP API at `/api`. Both run every action through the same command engine as the SSH cons
Everlock 0.6.0
The 0.6.0 release puts an AI assistant on equal footing with the admin console: every admin command is an MCP tool, authenticated with a new system-wide API key credential — and the whole admin surfac
Admin over MCP
The `backend-admin-mcp` outlet exposes every admin command as a Model Context Protocol tool over streamable HTTP, so an AI assistant administers the instance through the same engine as the SSH console
Administer Everlock from your AI assistant
Everlock's admin console now speaks MCP. The new `backend-admin-mcp` outlet exposes every admin command — around a hundred of them — as Model Context Protocol tools over streamable HTTP, so an AI assi
Server settings
`/server settings` in the [admin console](/docs/admin) is the single entry point for runtime-tunable, server-wide values. Settings live in the `everlock-system` store (`settings.json`), so every chang
Admin over SSH and CLI
The SSH admin surface is the implemented Everlock control plane today. It is provided by: - `frontend-ssh` - `backend-admin-ssh` This is a line-based admin REPL, not a shell. Commands begin with `/` a
Admin backends
Everlock has three admin surfaces over one command engine: - `backend-admin-ssh` — the interactive console - `backend-admin-http` — the web dashboard and the OpenAPI-described HTTP API with Swagger