Mechanics 0.1.57: addons become a service catalog
A focused look at the expanded addon catalog: PostgreSQL, S3-compatible buckets, Valkey caches, and NATS JetStream.
Read update →A focused look at the expanded addon catalog: PostgreSQL, S3-compatible buckets, Valkey caches, and NATS JetStream.
Read update →How dry runs, structured plans, user-commit protection, and repo deletion cascade make destructive operations inspectable.
Read update →How app info, logs, events, route diagnostics, image drift, and smoke-test headers made operations inspectable over SSH.
Read update →How Mechanics custom domains evolved before 0.1.57: CNAME proof, CDN-safe TLS, domain attach, diagnostics, and safe detach.
Read update →The route layer moved from basic exposure to GitOps-managed network state with Gateway API, TLS, redirects, sync, and wait.
Read update →How the per-user gitops repo became the audit trail for apps, routes, addons, and user-visible platform writes.
Read update →Mechanics gives users isolated namespaces, Argo CD projects, deploy keys, rollback access, and addon quotas without handing out kubeconfig.
Read update →How Mechanics introduced app instances with base and overlay layouts for main, prod, preview, and pull-request style deployments.
Read update →Why Mechanics shaped its SSH surface around explicit verbs, safe help, named flags, and shell-syntax rejection.
Read update →How signup, provisioning, and SSH client configuration became self-service and agent-friendly.
Read update →Mechanics started relaying git SSH traffic to Forgejo, making clone, fetch, and push part of the same authenticated platform front door.
Read update →How Mechanics connected CI, image publishing, build waits, app deploys, and public routes into one scriptable path.
Read update →A short note on what this update stream will track as Mechanics evolves.
Read update →