Шаблони застосунків і remix

Availability

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

Instantiation does not deploy app. Declared databases, buckets, authentication services not provisioned automatically. Some declared services stub-only, manifest declaration not evidence 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, declared services. Review repository, current revision, license, maintenance state, runtime commands before instantiation. Manifest 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 and returns app_id, source information, runtime type, declared services. Only keys declared by manifest accepted. Secret fields not seeded by call.

After instantiation:

1. inspect new app source and runtime settings;
2. supply secrets through App environment variables;
3. provide real external dependencies yourself unless service explicitly reported ready;
4. call deployment endpoint; and
5. follow deployment through build, health check, 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 and marked remixable. New app private.

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

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

Publication checklist for template

Before presenting template as usable:

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