메뉴
Installs self-hosted Eddytor on a single host with Docker Compose using the public prebuilt images. Activates for self-hosting on one VM, docker compose, the get.eddytor.dev installer, single-server Eddytor, or "no Kubernetes" — the simplest deployment path.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | eddytor-deploy-compose |
| description | Installs self-hosted Eddytor on a single host with Docker Compose using the public prebuilt images. Activates for self-hosting on one VM, docker compose, the get.eddytor.dev installer, single-server Eddytor, or "no Kubernetes" — the simplest deployment path. |
| license | CC-BY-NC-4.0 |
| metadata | {"author":"eddytor","version":"1.0"} |
The simplest self-host path: one VM running server + engine + Postgres via Compose,
using the public community images (ghcr.io/nordalf/..., :latest / :VERSION).
Consume prebuilt artifacts — never clone or build (that's a maintainer-only path).
For horizontal scale or managed cloud, use the Kubernetes skills instead (eddytor-deploy-helm).
curl get.eddytor.dev | sh
The installer downloads docker-compose.yml + install.sh from the GitHub release,
prompts for configuration, writes .env, and brings the stack up. Then create the first
admin (see below).
deploy/selfhost/docker-compose.yml from the GitHub release (don't build it)..env with the three required secrets + your public URL:EDDYTOR_DATABASE_URL=postgres://eddytor:eddytor@postgres:5432/eddytor
EDDYTOR_ENCRYPTION_KEY=<base64 of 32 random bytes> # openssl rand -base64 32
EDDYTOR_API_KEY_SECRET=<32+ random bytes> # openssl rand -base64 32
EDDYTOR__SERVER__PUBLIC_URL=https://eddytor.example.com
docker compose up -ddocker compose exec eddytor-server eddytoradm setup --email you@example.com --org "Your Org"
The UI is an opt-in Compose profile. The installer knob EDDYTOR_WITH_UI=true writes
COMPOSE_PROFILES=ui, EDDYTOR_UI_VERSION, and EDDYTOR__SERVER__WEB_REDIRECT_URIS into
.env. The UI image (ghcr.io/nordalf/eddytor-ce-ui) versions on its own cadence.
Binaries bind plaintext (h2c); terminate TLS at the edge — a Caddy overlay (see the
shipped community.tls.toml) or any reverse proxy in front of port 8080.
:latest / :VERSION). The :k8s tags are for the Helm
chart (DNS engine discovery) and won't fit the Compose engine.host direct-TCP wiring.get.eddytor.dev serves the published release asset, not your local checkout — fixes
land only when a new version is tagged.engine.host (the eddytor-engine service in
Compose) over plaintext on the host network — keep the ports off the public internet;
expose only the edge TLS proxy.EDDYTOR_ENCRYPTION_KEY safe — losing it makes
stored secrets unrecoverable.Onboards new users to the Eddytor MDM platform via MCP connection, authentication, and first table creation. Activates for Eddytor onboarding, MCP setup, workspace exploration, or first table creation — even without the phrase "getting started."
Deploys self-hosted Eddytor on Azure Kubernetes Service (AKS). Builds on eddytor-deploy-helm — only the Azure-specific deltas live here. Activates for AKS, Azure Kubernetes, az aks, deploy on Azure, Azure Database for PostgreSQL Flexible Server, Azure Blob storage, or quota/vCPU errors during cluster creation.
Installs self-hosted Eddytor on any Kubernetes cluster using the published OCI Helm chart. Activates for deploying Eddytor on Kubernetes, Helm install, the eddytor chart, ingress/TLS, external vs bundled Postgres, or scaling the engine — cluster-agnostic. Cloud-specific skills (AKS/GKE/EKS/Hetzner) build on this one.
Backup, restore, and secret rotation for self-hosted Eddytor. Activates for backup, restore, disaster recovery, key rotation, rotate secrets, the encryption key (EDDYTOR_ENCRYPTION_KEY), the API key secret (EDDYTOR_API_KEY_SECRET), OAuth signing keys, Postgres backups, or recovering a lost admin key.
Deploys self-hosted Eddytor on Amazon EKS — the AWS-specific deltas on top of the cluster-agnostic Helm skill. Activates for EKS, Elastic Kubernetes Service, eksctl, deploy on AWS, RDS for Postgres, S3 object store, ALB/NLB ingress, or IRSA — even without the phrase "deploy on EKS."
Deploys self-hosted Eddytor on Hetzner Cloud — the budget path. Hetzner has no managed Kubernetes, so you bring your own k3s (hetzner-k3s or k3sup) plus the Hetzner Cloud Controller Manager and hcloud-csi driver, then install the chart. Activates for Hetzner, hcloud, hetzner-k3s, k3s on Hetzner, Hetzner Object Storage, Hetzner Load Balancer, or "cheapest way to self-host Eddytor."