Files
hemx/examples/saas/README.md
T
slhx agent bf6add03ef docs(recipes): add deploy versioning boundary
Document deployment and version compatibility for hemx apps: release unit, runtime asset caching, rolling deploy policy, fingerprint mismatch behavior, semver buckets, upgrade notes, and deployment checks without adding platform code to core.

req: abi/001

req: abi/002

req: abi/003

req: abi/004

req: abi/005

req: runtime/004

req: failure/005
2026-06-05 09:32:25 +02:00

1.2 KiB

hemx SaaS tutorial skeleton

This is the compile-tested skeleton for the v1 production-shaped tutorial app. It is intentionally provider-light: auth/session, CSRF, persistence, deploy, metrics, and islands are explicit app boundaries, not hemx core services. req: examples/001 req: auth/001

What it proves today:

  • typed form/newtype inputs for project creation
  • auth/session context passed through normal Rust state
  • CSRF-safe mutation checked before persistence
  • local in-memory persistence adapter instead of a vendored SQL/auth provider
  • generated form, slot, keyed row, page-swap, and live-status commands
  • page shell with plain CSS and one explicit metrics island script
  • compile-time surface generation plus interaction tests

For provider-explicit boundaries, see ../../docs/recipes/sqlx-persistence.md, ../../docs/recipes/auth-session-csrf.md, and ../../docs/recipes/deploy-versioning.md.

What it deliberately does not claim yet:

  • a checked-in SQLx migration crate or database pool
  • production cookie/session middleware
  • a deploy target, flags, analytics, billing, or offline sync
  • browser automation for the metrics island

Run:

cargo run -p hemx-saas-example
cargo test -p hemx-saas-example