Repository navigation
Data Model
Krasnikov Maksim edited this page Oct 22, 2026
·
1 revision
| Entity | Key fields | Notes |
|---|---|---|
| Workspace |
name, unix_user, uid, subuid_range, home, env (prod/dev), cpu_slice
|
Isolation and resource boundary |
| Project |
workspace_id, name, git_repo, git_key_id
|
Groups services of one repository |
| Service |
project_id, name (alias), kind (stateless/stateful), image or build, template_id, resources, isolated
|
kind selects the deploy strategy |
| Deployment |
service_id, image_digest, git_sha, status, started_at, finished_at
|
Version history, rollback target |
| Port |
service_id, container_port, published, host_ip, host_port
|
Nothing is published without published=true
|
| Network / Link |
workspace_id; link: from_service, to_service, host_addr
|
Cross-workspace links are visible and revocable |
| Domain / Route |
service_id, domain, public_ip, tls_mode, upstream
|
Generates the Caddy config |
| Secret |
scope (workspace/service), name, encrypted_value, version
|
Value goes into podman secret
|
| EnvVar |
service_id, key, value or ref ({{postgres.url}}) |
References are resolved by the panel, not by a human |
| DbUser |
service_id (the DB), role (admin/app/readonly), secret_id
|
Password rotation restarts dependents |
| BackupJob |
service_id, schedule, target (S3), retention, last_status
|
systemd timer |
| Token |
scopes (read/plan/apply), workspace_ids, owner
|
For API, MCP, Telegram |
Maurice PaaS · Apache 2.0 · Repository · Task board