Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Development

Development documentation covers workflows that exist to build, validate, or exercise Nixstasis locally. These docs are not production operating procedures.

Local Stack

  • Compose Dev Harness describes the local deployment-shaped stack for validating Caddy TLS approval, FRP, managed device simulation, and browser-launched SSH terminal flows.
  • Production deployment belongs in Deployment Compose; this section is for local validation and developer feedback loops.
  • Default laptop mode uses local hostnames and local/internal Caddy certificates so developers can exercise application behavior without public DNS or public certificate issuance.
  • Optional public-fidelity validation can use DuckDNS or an operator-owned domain when public ACME behavior needs to be tested.

Accessibility

All user-facing features must meet WCAG 2.1 AA accessibility targets. This includes contrast ratios, keyboard focus visibility, form labels, error announcements, and modal dialog behavior.

Validation Boundaries

  • Local development should preserve the production-shaped boundary where browser traffic reaches Phoenix through Caddy.
  • Terminal testing should exercise LiveView, Phoenix Channels, server-side SSH, FRP TCP mux, and the managed client path instead of direct shell shortcuts.
  • Development-only certificates, local keys, generated Compose overrides, and runtime state stay out of source control.

Open Questions

  • Operational Unknowns tracks open implementation and operations questions that should be resolved before promoting a workflow to production guidance.