App Templates and Remixes

Verfügbarkeit

Template manifest und app-record workflow ist implementiert. Can list operator-curated manifests, create new app record from one, seed non-secret environment values when environment store configured, und create clean remix record from eligible app.

Instantiation deploys app nicht. Declared databases, buckets und authentication services not provisioned automatically. Some declared services themselves stub-only, manifest declaration kein Nachweis dependency exists.

Browse manifests

GET /api/apps/templates?category=web&q=next
GET /api/apps/templates/{template_id}

Gallery public-read. Manifest describes source Git URL, branch, runtime defaults, environment-variable schema und declared services. Review repository, current revision, license, maintenance state und runtime commands before instantiation. Manifest ist operator metadata, not security endorsement.

Two built-in seed manifests make API non-empty. External repositories can change or disappear, not yet automated smoke test for every seed.

Instantiate

POST /api/apps/templates/{template_id}/instantiate
Content-Type: application/json
 
{
  "name": "My app",
  "env": {
    "NEXT_PUBLIC_APP_NAME": "My app"
  }
}

Call creates private app record und returns app_id, source information, runtime type und declared services. Only keys declared by manifest accepted. Secret fields not seeded by this call.

After instantiation:

1. inspect new app source und runtime settings;
2. supply secrets through App environment variables;
3. provide real external dependencies yourself unless service explicitly reported ready;
4. call deployment endpoint; und
5. follow deployment through build, health check und activation.

Remix

POST /api/apps/{source_app_id}/remix
Content-Type: application/json
 
{
  "name": "My private remix"
}

Owners may remix own app. Another user may remix only app both public und marked remixable. New app private.

Remix carries source URL, branch, deployment type, port und lineage. Deliberately does not copy environment values, secrets, database or bucket references, authentication bindings, checkpoints, IDE state oder data. Forks or pins remote Git repository nicht. If source owner later changes or removes repository, new deployment can differ or fail.

For durable remix, fork source into repository you control, review und pin revision, update new app source, then deploy.

Publication checklist for template

Before presenting template as usable:

• confirm repository und license;
• pin or record tested revision;
• validate install, build, run, port und health behavior;
• test required environment fields without exposing secrets;
• verify every declared service actually available; und
• instantiate, deploy, smoke-test und remove in clean environment.