Skip to content
Discussion options

You must be logged in to vote

I’ve run Dokploy in production on a few internal tools while it was still 0.x, and it’s been solid enough for non‑critical workloads. The main risk isn’t stability - most 0.x releases have been well tested - but breaking changes between minor versions, since semver isn’t locked until 1.0. If you need a stable base, pin to a specific version tag (e.g., v0.12.3) or a commit SHA in your Docker image or Helm chart, and review the changelog before each upgrade. For anything customer‑facing or with SLAs, I’d wait for the first 1.0 release or maintain a separate staging cluster to catch incompatibilities early. Otherwise, treat it like any other pre‑1.0 project: monitor, pin, and test upgrades r…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by jux-stef
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants