Write a self-hosting guide for Coolify users migrating to Dokploy + konnos #2

New issue

Open

opened 2026-05-08 20:40:08 +02:00 by flndrn · 0 comments

flndrn commented

2026-05-08 20:40:08 +02:00

Owner

Why

A few people coming to konnos are migrating off Coolify (community references in older docs are outdated). Dokploy is konnos's primary deploy path (CLAUDE.md hard rule 9). A migration guide would shorten time-to-first-deploy substantially.

Scope

A new doc at docs/migrate-from-coolify.md covering:

What's the same (Docker compose conventions, Traefik, env-var injection).
What's different (Dokploy's compose-vs-application split, Swarm-mode services, project/environment hierarchy).
Step-by-step: export from Coolify → import into Dokploy → wire to konnos as Git source.
Common pitfalls (port collisions, dokploy-network membership, webhook re-registration).

Acceptance criteria

Doc exists at docs/migrate-from-coolify.md.
At least one verified migration (your own, or a friend's) — document the steps you actually took.
Linked from README.md in the quickstart section.

Pointers

Existing doc structure: nothing yet in docs/ — you're shaping the convention.
Example compose for Dokploy: docker-compose.yml at the repo root.

Friendly note: maintainer hasn't done a Coolify migration personally. Your firsthand experience is more valuable here than the maintainer's edits would be.

## Why A few people coming to konnos are migrating off Coolify (community references in older docs are outdated). Dokploy is konnos's primary deploy path (CLAUDE.md hard rule 9). A migration guide would shorten time-to-first-deploy substantially. ## Scope A new doc at `docs/migrate-from-coolify.md` covering: 1. What's the same (Docker compose conventions, Traefik, env-var injection). 2. What's different (Dokploy's compose-vs-application split, Swarm-mode services, project/environment hierarchy). 3. Step-by-step: export from Coolify → import into Dokploy → wire to konnos as Git source. 4. Common pitfalls (port collisions, dokploy-network membership, webhook re-registration). ## Acceptance criteria - [ ] Doc exists at `docs/migrate-from-coolify.md`. - [ ] At least one verified migration (your own, or a friend's) — document the steps you actually took. - [ ] Linked from `README.md` in the quickstart section. ## Pointers - Existing doc structure: nothing yet in `docs/` — you're shaping the convention. - Example compose for Dokploy: `docker-compose.yml` at the repo root. Friendly note: maintainer hasn't done a Coolify migration personally. Your firsthand experience is more valuable here than the maintainer's edits would be.