Skip to content

[casting] Dokploy with Docker Compose #84

@Nageshbansal

Description

@Nageshbansal

Deployment platform

dokploy

Deployment mode

NA

Deployment flavor

stack

Why this Casting?

Dokploy is a self-hosted PaaS (388+ templates) that deploys applications via Docker Compose. A Foundry casting would generate a Dokploy-compatible Compose file with the required dokploy-network and Traefik labels, letting users deploy SigNoz from the Dokploy dashboard or add it to Dokploy's template marketplace.

Proposed Casting configuration

apiVersion: v1alpha1
  metadata:
    name: signoz
  spec:
    deployment:
      platform: dokploy
      flavor: stack

Expected Pours structure

pours/deployment/
    compose.yaml
    telemetrykeeper/
      clickhousekeeper/
        keeper-0.yaml
    telemetrystore/
      clickhouse/
        config.yaml
        functions.yaml
    ingester/
      ingester.yaml
      opamp.yaml

Tooling requirements

None (forge-only, manual deployment via Dokploy dashboard)

References

Additional context

Similar to the Coolify casting, this is a forge-only casting (cast is a no-op). The generated Compose file must use dokploy-network (external) and include Traefik labels for the SigNoz UI service. container_name must not be set on any service as it breaks Dokploy's logs/metrics features

Metadata

Metadata

Assignees

No one assigned

    Labels

    castingIssues related to casting.enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions