Get Your Own Terminology Server
Run a FHIR R4 SNOMED CT terminology server on a clean VPS with Docker Compose - HTTPS included. Either route produces the same stack: sct (builds the database on first boot and serves FHIR) behind Caddy (automatic TLS, optional basic auth, CORS). Caddy owns the public ports; sct is never reachable directly. See spec/deployment.md for the design rationale.
Pick a route:
| Docker Image | Build From Source | |
|---|---|---|
Needs git |
No | Yes |
| Needs a local build | No - pulls pacharanero/sct from Docker Hub |
Yes - docker compose up --build |
| Files to fetch | 4 (compose file, Caddyfile, entrypoint script, env template) | Whole repo, via git clone |
| Upgrade | docker compose pull && docker compose up -d |
git pull && docker compose up -d --build |
| Pick this when | You just want the server running | You want to patch the code, pin a commit, or build for an unpublished platform |
Most people want Docker Image - it's the fastest path to a running server. Reach for Build From Source if you need to change or audit the code you're running.