Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

README.md

Coolify Stack

Field Value
Mode -
Flavor stack
Platform coolify

Overview

Generates a coolify.yaml stack definition for deploying SigNoz on a Coolify-managed server. Deployment is manual via the Coolify dashboard.

Note

foundryctl cast does not deploy to Coolify automatically. It generates the files and prints instructions for manual deployment.

Prerequisites

  • A Coolify instance (self-hosted or cloud)

Configuration

apiVersion: v1alpha1
kind: Installation
metadata:
  name: signoz
spec:
  deployment:
    flavor: stack
    platform: coolify

Deploy

# Generate the stack definition
foundryctl forge -f casting.yaml

After forging, deploy the generated coolify.yaml using the Coolify stack feature.

Nothing is published on host ports. Coolify routes each endpoint through a magic environment key, and you assign its domain in the Coolify dashboard: SERVICE_URL_SIGNOZ0_8080 for the UI, SERVICE_URL_INGESTER0_4318 for OTLP HTTP, and SERVICE_URL_MCP0_8000 for the MCP server. OTLP gRPC on port 4317 is reachable only inside the stack unless a patch adds a host port.

Generated output

pours/deployment/
  coolify.yaml

MCP server (optional)

Foundry can deploy the SigNoz MCP server alongside the stack so AI clients can query your telemetry. It is disabled by default; enable it in the casting:

apiVersion: v1alpha1
kind: Installation
metadata:
  name: signoz
spec:
  deployment:
    flavor: stack
    platform: coolify
  mcp:
    spec:
      enabled: true

This adds a signoz-mcp-0 service to the stack listening on port 8000, carrying the SERVICE_URL_MCP0_8000 key. Assign a domain for it in the Coolify dashboard to reach it from AI clients; the MCP endpoint is that URL plus /mcp.

To connect an AI client (mint an API key, configure Claude Code or Claude Desktop), see MCP server.

Customization

For changes to the generated coolify.yaml, use patches.