Parse Server Template

Full Parse Server scaffold — Dockerfile, src/, GitHub Actions workflows.

• Repo: dps-templates-parse-server
• Docker image: ghcr.io/duabalabs/parse-server (latest, 7.0.0, 6.5.0, 6.4.0)
• Path: apps/dps/dps-templates/dps-templates-parse-server
• Status: ✅ 100%

What it includes

• Parse Server + Express bootstrap.
• Dockerfile + docker-compose.yml with env_file (MongoDB included for self-hosted, excluded for DPS-hosted where MongoDB is provisioned externally).
• GitHub Actions workflow for build + push to ghcr.io/duabalabs.
• Sample cloud/ directory with main.ts entry.
• Pre-wired parse-dashboard for the /dashboard route.

How DPS uses it

When a customer creates a parse-server app:

1. The wizard (ParseInstanceCreateDialog.tsx) collects name, region, tier, and optional GitHub repo.
2. dps_createParseInstance provisions the container via docker-orchestrator.ts.
3. The image (ghcr.io/duabalabs/parse-server:<version>) is pulled.
4. Environment variables (PARSE_APP_ID, PARSE_MASTER_KEY, DATABASE_URI) are injected.
5. Nginx + SSL (Certbot) are configured for the customer subdomain.
6. The instance is registered in the master DPS database with health check + metrics.

If the customer connected a GitHub repo, the template is forked into their account and DPS subscribes to push webhooks for redeploys.

Configuration fields

The wizard exposes these fields (defined in templates.ts):