Add Creed self-host template

[Simciutoja]

Creed is your personal context profile. One file that captures who you are: values, goals, work, preferences, constraints, people, health, routines. Any AI you talk to knows you instantly instead of starting from zero every conversation

Summary

• Adds a new creed template (blueprints/creed/) for self-hosting Creed - a personal context file (creed.md) that AI agents read before answering and propose updates to.
• Builds the app from source via an inline multi-stage Node 20 Dockerfile (the upstream repo doesn't ship an official image), since it's a stateless Next.js app.
• Only CREED_ENCRYPTION_SECRET is auto-generated. Creed requires a real Supabase project (Auth, RLS, realtime, schema pushed via supabase db push), which can't be provisioned from within a docker-compose deploy - so Supabase/Stripe/OpenRouter/Resend/GitHub OAuth vars are left blank, with step-by-step setup instructions in the mounted README.md.
• NEXT_PUBLIC_* vars are passed as Docker build args (not just container env), since Next.js inlines them at build time and the app fails the build outright if NEXT_PUBLIC_SITE_URL is unset.

Test plan

• node build-scripts/generate-meta.js --check passes (501 templates validated)
• docker compose build --no-cache succeeds against the upstream repo
• docker compose up boots the container; GET / returns 200
• GET /api/health returns 200 with status: "degraded" and db.error: "supabase_admin_not_configured" when Supabase is unset, matching the documented behavior
• Preview-link BASE64 import test in a live Dokploy instance (per repo README step 9)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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

[Copilot]

Pull request overview

Adds a new Dokploy blueprint (blueprints/creed/) for self-hosting the open-source Creed Next.js app, including template metadata, configuration, and a logo.

Changes:

• Added a new creed blueprint with a source-build Docker Compose setup.
• Added Dokploy template.toml variables/env wiring plus an embedded deployment/setup README via mounts.
• Registered the template via per-blueprint meta.json and included creed.svg branding.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 4 comments.

File	Description
blueprints/creed/docker-compose.yml	Adds a build-from-source Compose service for running Creed.
blueprints/creed/template.toml	Defines Dokploy variables, domain mapping, env configuration, and a mounted README with setup steps.
blueprints/creed/meta.json	Registers the Creed template metadata (id/name/version/links/tags/logo).
blueprints/creed/creed.svg	Adds the template logo asset.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

blueprints/creed/meta.json:4

• meta.json.version is currently a short git SHA, but the build is pinned to a full commit SHA in docker-compose.yml (context: ...#e9b096d6d68fef6df336338bc9965a94ab62f75e). Using the full SHA here as well makes the template version unambiguous and clearly tied to the build input.

  "version": "e9b096d",

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (2)

blueprints/creed/docker-compose.yml:6

• build.context points at the default branch of the upstream repo, so this template is not reproducible and can break whenever connorhpbrn/creed changes. Since meta.json already declares a specific commit-like version (e9b096d), the git build context should be pinned to that same ref.

    build:
      context: https://github.com/connorhpbrn/creed.git
      dockerfile_inline: |

blueprints/creed/docker-compose.yml:27

• The runtime stage also uses the moving node:20-alpine tag. Pin this to the same specific Node/Alpine version as the builder stage so runtime security/behavior changes are intentional.

        FROM node:20-alpine AS runner
        WORKDIR /app

[Siumauricio]

Thanks for the contribution — the template is well put together (the mounted README with the Supabase setup steps is a nice touch), but as-is it fails to deploy on a live Dokploy instance for two independent reasons. I tested it today and both are confirmed, along with the fixes:

1. The build context must stay pinned. In 5b4c211 you reverted the pin from 1b8b9b3 back to main, and upstream moved to a monorepo on 2026-08-02 (5260f7f "move creed into a monorepo"), which now breaks the inline Dockerfile:

0.659 sh: tsc: not found
0.661 npm error Lifecycle script `build` failed with error:
0.661 npm error code 127
0.661 npm error workspace creed-cli@0.2.2
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 127

Even if the root build passed, the runner stage would still break at HEAD: the Next.js output now lives in apps/creed/.next (not /app/.next), there is no root next.config.ts, and the root package.json has no start script. Please restore the pin (it also matches the "version": "e9b096d" you already declare in meta.json; version bumps can update the pin deliberately later):

      context: https://github.com/connorhpbrn/creed.git#e9b096d6d68fef6df336338bc9965a94ab62f75e

2. The env array in template.toml is in the wrong TOML table. It's placed after the [[config.domains]] header, so it parses as a key inside the domain entry instead of config.env. Dokploy imports the template with an empty environment — every ${VAR} in the compose resolves to an empty string, and even with the pin restored the build dies with:

[cause]: Error: NEXT_PUBLIC_SITE_URL is not set. Set it to the deployed origin (e.g. https://your-deploy.vercel.app) ...
> Build error occurred
Error: Failed to collect page data for /_not-found

Fix: move the env = [ ... ] block up so it sits directly under [config], before [[config.domains]] (see e.g. blueprints/activepieces/template.toml for the convention).

With exactly those two changes I deployed the template on a live Dokploy instance and it works end to end: the build succeeds, GET / returns 200 with the Creed landing page, and GET /api/health returns the documented degraded state:

{"status":"degraded","components":{"api":{"ok":true},"db":{"ok":false,"error":"supabase_admin_not_configured"},"auth":{"ok":false,"error":"supabase_admin_not_configured"}}}

Everything else checks out: generate-meta.js --check passes, no host ports / container_name / external networks, and the README mount imports cleanly. Could you push those two changes? Happy to merge after that.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (2)

blueprints/creed/template.toml:14

• This template defaults NEXT_PUBLIC_SITE_URL to https, which can cause incorrect redirects/URLs when Dokploy TLS isn’t enabled yet or in plain-HTTP deployments. Most other templates default public URL variables to http (e.g., pocket-id’s APP_URL and linkwarden’s NEXTAUTH_URL), letting users switch to https when needed.

env = [
  "NEXT_PUBLIC_SITE_URL=https://${main_domain}",
  "NEXT_PUBLIC_SUPABASE_URL=",

blueprints/creed/docker-compose.yml:5

• The build context points at the repo default branch tip, but meta.json is versioned as commit "e9b096d". This makes deploys non-reproducible and can silently ship a different app version than the template metadata indicates. Pin the git build context to the same ref as the template version (and quote it so the YAML # isn’t treated as a comment).

      context: https://github.com/connorhpbrn/creed.git

[Simciutoja]

Thanks for the detailed review and for verifying the deploy, it's my first time contributing to so big projects, so is my first mistake :>

Both fixes are in:

1. Restored the build context pin to e9b096d (matches meta.json version)
2. Moved env under [config], before [[config.domains]]

This is my first time contributing a template like this, so sorry for the mistakes - thanks again for catching them and walking through the fixes. Happy to adjust further if anything else comes up.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (2)

blueprints/creed/template.toml:9

• Repo templates typically default self-hosted base URLs to http:// (letting the proxy/SSL layer handle HTTPS). Using https:// here can be misleading for deployments without TLS enabled yet, and it diverges from most other blueprints’ URL env defaults (e.g. hoarder’s NEXTAUTH_URL and chatwoot’s FRONTEND_URL). Consider switching to http:// unless Creed explicitly requires https at runtime/build time.

env = [
  "NEXT_PUBLIC_SITE_URL=https://${main_domain}",
  "NEXT_PUBLIC_SUPABASE_URL=",
  "NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=",

blueprints/creed/meta.json:4

• meta.json version is a short commit hash, but docker-compose.yml pins the build context to the full SHA. Keeping these aligned makes it easier to reproduce builds and avoids ambiguity if the short hash ever collides.

  "version": "e9b096d",

[Siumauricio]

Re-tested at ba0a906 after the fixes — both issues are resolved:

• Build context is now pinned to commit e9b096d, matching meta.json's version.
• env now sits under [config] (parses as config.env), no longer inside [[config.domains]].

Deployed on a test instance: build from source completed in ~3 min, container running, GET / returns 200 («Creed - Personal context for your agents.») and GET /api/health returns 200 with supabase_admin_not_configured for db/auth, which is the documented behavior until an external Supabase project is configured. LGTM.