Generated from corpus/lines/software/units/sw.pattern.dynamic-web.md. Do not edit by hand — run python scripts/generate-corpus-docs.py.

sw.pattern.dynamic-web

Status: draft (D3-aligned)
Sources: Lab/Runtime AGENTS; D3; historical hectorsanchez.eu dynamic pattern (superseded layout)

Place in pattern family

Same CI/CD choreography (sw.lifecycle.deploy). Differs in backend process + nginx proxy + shared host .env. Default process model: socket activation (sw.ops.socket-activation); always-on only with documented reason.

When to use

• Long-running server / same-host API / MCP HTTP on konstant.
• Server-held config in shared .env.
• Not a fit for Vercel-only static/serverless (use sw.pattern.vercel or split front/back).

Guardrails

• Standalone app repo; nginx TLS → local backend.
• Prefer socket activation; document always-on exceptions.
• Secrets on host / Actions — never in git.
• Live verify before any Lab catalog entry.

Historical note

Old monorepo content/lab/ + proxy/ layouts are not authoritative.

Prohibited

• Secrets in the repo
• Always-on HTTP without documented exception
• Decommissioned VPS as target