# DocuSeal Deployment on Core

Deployed Jul 7, 2026 via Docker on Core (netcup, 152.53.192.33).

## Docker Compose

```yaml
services:
  docuseal:
    image: docuseal/docuseal:latest
    container_name: docuseal
    restart: always
    ports:
      - "127.0.0.1:3000:3000"
    volumes:
      - ./data:/data
    environment:
      - HOST=http://localhost:3000
      - FORCE_SSL=false
```

Location: `/root/docker/docuseal/docker-compose.yml`
Data: `/root/docker/docuseal/data/`

## HTTPS

Caddy reverse proxy at https://sign.itpropartner.com → 127.0.0.1:3000

Caddy config at `/etc/caddy/Caddyfile`:
```
sign.itpropartner.com {
    reverse_proxy 127.0.0.1:3000
}
```

## API

Token: created in DocuSeal UI (Settings → API Tokens). Linked to info@itpropartner.com.

Test: `curl -s -H "X-Auth-Token: <token>" https://sign.itpropartner.com/api/user`

## Key decisions

- DocuSeal chosen over Documenso for this use case (AGPL, free embedding SDKs, Docker image 227MB, SQLite, no PostgreSQL needed)
- Both self-hosted options are ESIGN Act / UETA compliant
- Documenso would require ~$300/yr for embedding SDKs and PostgreSQL — overkill for this scale
- Dual use: family via web UI, DRE portal via API
