Get started

Transparent and ongoing

ChangelogDocumented releases at a glance.

Release history follows CHANGELOG.md exclusively. The current product may include more functionality; features are not attributed to a historical release without documented evidence.

Get startedFAQ
  1. 1.0.0-rc.1Release Candidate

    Stability, data and clear responsibilities.

    The candidate strengthens project state, imports and dependency handling. Package and Docker checks form part of the release requirements.

    • Credentials, data namespaces and snapshots are preserved independently of disposable runtime state.
    • Imports are validated against the canonical schema; filesystem, CMS, registry and runtime changes roll back together.
    • Database and archive data are streamed. Process arguments are structured and npm installs account for locks.
    • Verified stack generators and runtime images are pinned; PHP requirements are checked in real FPM containers.
    • Domain, stack adapters, dependencies, Compose, gateway and command registration have separate responsibilities.
    • The CLI is built as an ESM package with clear TypeScript boundaries and no library exports.
    • Lint, coverage, cross-platform package smoke tests and native Docker release gates were added.
  2. 1.0.0-beta.3Internal milestone

    Dwell as a standalone CLI.

    Dwell was separated from the previous tool under the package name @websign/dwell. The direct CLI provides the foundation for further development.

    • A standalone CLI under @websign/dwell.
    • Commands run directly through dwell; the former umbrella subcommands and plugin surface are removed.
    • Project state lives in .dwell/dwell.json, runtime assets in .dwell/, and global gateway state in ~/.dwell/.
    • Local .localhost routes and optional LAN .local routes retain their behaviour.
    • This milestone starts with fresh project and gateway state; no migration or cleanup is performed.
Read the full changelog on GitHub

dwell artifact

Prepare production files.

Generate separate output in artifact/ for supported combinations. Your source stays unchanged. No production server connection, upload, deployment or server configuration.