Add Open Design template

[abhishukla610]

Add Open Design template

Open Design is a local-first, open-source design tool with native desktop apps, a large library of design systems, and an extensible plugin ecosystem that runs across many coding agents. It ships as a single self-contained container (no external database or cache required).

What's included

• blueprints/open-design/docker-compose.yml — single open-design service on ghcr.io/nexu-io/od:latest, listening on internal port 7456, with a persistent volume at /app/.od and a /api/health healthcheck.
• blueprints/open-design/template.toml — domain mapping + auto-generated OD_API_TOKEN (${password:32}) and OD_ALLOWED_ORIGINS set to the assigned domain.
• blueprints/open-design/open-design.svg — official logo.
• meta.json — new entry (alphabetically placed between ontime and open-fiesta).

Notes

• Follows the blueprint rules: no container_name, no explicit ports:, no custom networks; Traefik routing is handled via the [[config.domains]] block on port 7456.
• The app requires an API token; the template auto-generates one and scopes OD_ALLOWED_ORIGINS to the deployed domain so it works behind Dokploy's reverse proxy out of the box.

Testing

• node dedupe-and-sort-meta.js → passes.
• docker compose -f blueprints/open-design/docker-compose.yml config → valid.
• Confirmed the template renders in the preview catalog and produces a valid importable Base64 config.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	443e944

[chatgpt-codex-connector]

💡 Codex Review

templates/blueprints/nextcloud-aio/docker-compose.yml

Lines 8 to 12 in 61bf8e1

	environment:
	- MYSQL_HOST=nextcloud_db
	- MYSQL_DATABASE=nextcloud
	- MYSQL_USER=nextcloud
	- MYSQL_PASSWORD=${MYSQL_PASSWORD}

Pass the Nextcloud runtime envs into the service

The template now defines NEXTCLOUD_DOMAIN, OVERWRITEPROTOCOL, TRUSTED_PROXIES, and REDIS_HOST in template.toml, but this service only forwards the MySQL variables into the Nextcloud container. The official image consumes settings such as NEXTCLOUD_TRUSTED_DOMAINS, OVERWRITEPROTOCOL, and REDIS_HOST only from the container environment (see https://hub.docker.com/_/nextcloud), so fresh Dokploy installs silently ignore the public-domain/proxy/Redis configuration and can end up with untrusted-domain or wrong-protocol behavior. Please pass those variables here, e.g. NEXTCLOUD_TRUSTED_DOMAINS=${NEXTCLOUD_DOMAIN} and OVERWRITEPROTOCOL=${OVERWRITEPROTOCOL}.

---

templates/blueprints/mediafetch/template.toml

Lines 7 to 10 in 61bf8e1

	name = "Domain"
	variable = "DOMAIN"
	serviceName = "mediafetch"
	port = 3002

Restore the required MediaFetch domain host

This new domain block omits the required host field and uses name/variable instead. Dokploy's template structure requires serviceName, port, and host for each domain (https://github.com/Dokploy/templates/blob/canary/README.md), so the template importer will not have a host to route MediaFetch to, and the compose value PUBLIC_BASE_URL=https://${DOMAIN} remains unset. Use a normal domain variable such as main_domain = "${domain}", set host = "${main_domain}", and export DOMAIN=${main_domain} through config.env if the container needs it.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".