Caddy Panel

Sites

Caddy

Containers

Uptime

Sites

Domain	Type	Target	Status	Actions

Docker Containers

Container	Image	Status	Ports	Network	Actions

Auto-Deploy Projects

Project	Repository	Branch	Last Deploy	Status	Actions

Setup: Add your project here, then go to your GitHub repo → Settings → Webhooks → Add webhook.
Payload URL: https://panel.sdmr.dev/api/deploy/webhook | Content type: application/json | Events: Just the push event

Webhook Activity

Time	Event	Repository	Branch	Status	Details

Hostinger DNS API is not configured. Add HOSTINGER_API_TOKEN to your .env file.

Caddy Logs

New Application Setup Guide

All the steps needed to add a new project to the sdmr.dev infrastructure from scratch.

⚙

Architecture Overview

Internet (:80/:443)
    |
    v
 ┌──────────────────────────┐
 │  Caddy  (reverse proxy)  │   /root/caddy/
 │  Auto SSL / HTTPS        │   All traffic goes through here
 └────┬─────────┬─────────┬─┘
      │         │         │
      v         v         v
  ┌────────┐ ┌────────┐ ┌────────┐
  │ Proj 1 │ │ Proj 2 │ │ Proj 3 │   Each one is independent
  │  :3000 │ │  :4000 │ │  :8080 │   docker-compose
  └────────┘ └────────┘ └────────┘
      └─────────┴─────────┘
          "proxy" network

Key rule: Caddy is completely independent. No project's docker-compose file contains Caddy. Adding a new project doesn't require touching any other project.

☰

Step by Step Setup

Add DNS A Record

Create a new A record at your domain provider (or use the DNS tab in this panel).

Type	Name	Content	TTL
A	myproject	178.104.113.215	300

DNS propagation can take 5-30 minutes. Continue with the other steps while waiting.

Create Project Directory

Connect to the server and set up the project folder.

Terminal

ssh root@178.104.113.215

mkdir -p /root/myproject
cd /root/myproject
# git clone or create files

Write Dockerfile

Create an appropriate Dockerfile for your project type.

Dockerfile

FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
EXPOSE 3000
CMD ["node", "index.js"]

Dockerfile

FROM python:3.12-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
EXPOSE 8000
CMD ["python", "main.py"]

Dockerfile

FROM golang:1.22-alpine AS builder
WORKDIR /app
COPY go.* ./
RUN go mod download
COPY . .
RUN CGO_ENABLED=0 go build -o server .

FROM alpine:3.19
COPY --from=builder /app/server /server
EXPOSE 8080
CMD ["/server"]

Write docker-compose.yml

Connect your project to the proxy network. Don't expose ports externally.

docker-compose.yml

services:
  app:
    build: .
    container_name: myproject-app    # must be unique!
    restart: unless-stopped
    env_file: .env
    networks:
      - proxy

networks:
  proxy:
    external: true

Checklist

Is container_name unique? Has networks: proxy with external: true? No ports: defined? (don't expose externally) Is .env file created?

▶ Example with database

docker-compose.yml (with PostgreSQL)

services:
  app:
    build: .
    container_name: myproject-app
    restart: unless-stopped
    env_file: .env
    networks:
      - proxy
      - internal
    depends_on:
      - db

  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: mydb
      POSTGRES_USER: myuser
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - db-data:/var/lib/postgresql/data
    networks:
      - internal    # internal only!

networks:
  proxy:
    external: true
  internal:

volumes:
  db-data:

Don't connect the database to the proxy network. Access through internal network only.

Create Caddy Site Config

You can do this directly from this panel! Use the "+ New Site" button on the Dashboard tab.

Reverse Proxy Most common

Serve your app through a container.

Subdomain: myproject

Type: proxy

Target: myproject-app:3000

Static Site

Serve HTML/CSS/JS files directly.

Subdomain: blog

Type: static

Directory: blog (/srv/blog)

Or manually via terminal:

Terminal

cat > /root/caddy/sites/myproject.sdmr.dev << 'EOF'
myproject.sdmr.dev {
    reverse_proxy myproject-app:3000

    header {
        -Server
        X-Content-Type-Options nosniff
        X-Frame-Options DENY
    }
}
EOF

Start the Project

Build and run the container.

Terminal

cd /root/myproject
docker compose up -d --build

Caddy Reload

Activate the new site config. You can use the "Caddy Reload" button on the Dashboard or run it from the terminal.

Terminal

docker exec caddy caddy reload --config /etc/caddy/Caddyfile

Note: When you add a site through the panel, reload happens automatically. This step is only needed for manual config creation.

Verify

Check that everything is working properly.

Terminal

# Is the container running?
docker ps | grep myproject-app

# Was the SSL certificate obtained?
docker logs caddy --tail 10

# Is the site accessible?
curl -I https://myproject.sdmr.dev

Final Checklist

DNS record has propagated Container is in running state Caddy obtained SSL certificate HTTPS access from browser is successful

⚠

Important Rules

Container Naming

Each project's container_name must be unique. Caddy accesses containers by this name.

Project	container_name	Caddy target
altin-api	`haremaltin-api`	`haremaltin-api:3000`
caddy-panel	`caddy-panel`	`caddy-panel:3500`
new project	`myproject-app`	`myproject-app:3000`

Port Exposure

No project exposes ports externally. Only Caddy opens ports 80/443. Inter-container communication happens through the Docker proxy network.

Caddy Reload vs Restart

Use caddy reload, not docker restart caddy. Reload updates config with zero downtime, while restart causes brief downtime.

Quick Command Reference

Frequently Used Commands

# --- Caddy ---
docker exec caddy caddy reload --config /etc/caddy/Caddyfile   # Config reload (zero downtime)
docker exec caddy caddy validate --config /etc/caddy/Caddyfile  # Validate config
docker logs caddy --tail 20                                     # View Caddy logs

# --- Project ---
cd /root/project-name
docker compose up -d --build     # Build and start
docker compose down              # Stop and remove
docker compose logs -f           # Follow logs
docker compose restart           # Restart

# --- General ---
docker ps -a                     # All containers
docker network inspect proxy     # Proxy network details
docker system prune -f           # Clean unused images

Removing a Project

Terminal

# 1. Stop the project
cd /root/myproject
docker compose down

# 2. Delete the site from the panel (or manually)
rm /root/caddy/sites/myproject.sdmr.dev

# 3. Caddy reload
docker exec caddy caddy reload --config /etc/caddy/Caddyfile

# 4. (Optional) Delete DNS record and directory
rm -rf /root/myproject

Caddy Panel

Sites

Docker Containers

Auto-Deploy Projects

Webhook Activity

Add Deploy Project

Deploy Logs:

Webhook Setup

DNS Records

Add DNS Record

Caddy Logs

New Application Setup Guide

Architecture Overview

Step by Step Setup

Add DNS A Record

Create Project Directory

Write Dockerfile

Write docker-compose.yml

Create Caddy Site Config

Start the Project

Caddy Reload

Verify

Important Rules

Quick Command Reference

Removing a Project

Add New Site

Edit Site: