Skip to content

feat(casting): add Dokploy stack support - #175

Open
abhinavmathur-atlan wants to merge 4 commits into
SigNoz:mainfrom
abhinavmathur-atlan:feat/84-dokploy-casting
Open

feat(casting): add Dokploy stack support#175
abhinavmathur-atlan wants to merge 4 commits into
SigNoz:mainfrom
abhinavmathur-atlan:feat/84-dokploy-casting

Conversation

@abhinavmathur-atlan

@abhinavmathur-atlan abhinavmathur-atlan commented Aug 7, 2026

Copy link
Copy Markdown

Features

  • Add Dokploy as an installation platform with the stack flavor.
  • Generate a Docker Swarm compose.yaml, component configuration files, schemas, catalog entries, and Dokploy documentation.
  • Configure HTTPS routing with a required SIGNOZ_DOMAIN and Traefik labels.

Fixes

  • Base Dokploy output on the native Docker Swarm casting instead of Coolify-specific Compose extensions.
  • Keep databases on a private overlay network and attach only the SigNoz UI to dokploy-network.
  • Avoid host-published ports and make foundryctl cast a documented no-op for Dokploy.

Refactors

  • Reuse the existing Swarm forge and configuration-material pipeline for Dokploy stacks.

Tests

  • Add Dokploy forge and Cast no-op regression tests.
  • Run go test ./... and make docs.
  • Run the complete local CLI flow: foundryctl forge, byte-for-byte artifact comparison, docker stack config with a synthetic domain, and foundryctl cast.

Fixes #84

@Nageshbansal Nageshbansal added the safe-to-test Run CI on external PRs. label Aug 7, 2026
@Nageshbansal

Copy link
Copy Markdown
Member

Hey @abhinavmathur-atlan
It seems GitHub has updated its policy, which is causing issues with the CI. We'll look into what has changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe-to-test Run CI on external PRs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[casting] Dokploy with Docker Compose

2 participants