Skip to main content

Publish

publish produces optimized frontend assets plus the backend output needed to serve or deploy the application.

Command​

webstir publish --workspace /absolute/path/to/workspace

Outputs​

  • dist/frontend/** for optimized document assets when the workspace has a frontend surface
  • build/backend/** for compiled backend output when the workspace has a backend surface

Runtime Expectations​

  • Frontend assets are fingerprinted and rewritten for publish mode.
  • Backend routes still own HTML, redirect, and fragment behavior.
  • Request-time views continue to serve document HTML and expose x-webstir-document-cache.
  • Fragment responses stay uncached and continue to emit x-webstir-fragment-* headers.

Default Ship Path​

For the main server-first lane:

  1. Start from a full workspace.
  2. Validate the baseline document and form flow with watch and test.
  3. Run webstir publish --workspace "$PWD".
  4. Deploy the published workspace with the Bun Docker contract from Docker Deployment.

Proof App Validation​

Before changing docs or runtime behavior, confirm publish mode on the proof apps:

bun run publish:auth-crud
bun run publish:dashboard

Those two demos cover the shipped server-handled forms and dashboard refresh paths.

For static-site output, scaffold an ssg workspace, or keep the current workspace mode and force SSG publish with webstir publish --workspace /absolute/path/to/workspace --frontend-mode ssg. The lower-level webstir-frontend publish --mode ssg package CLI still works directly when you need package-level control.

For published api and full workspaces, use the supported Bun Docker deployment contract described in Docker Deployment. Webstir is still experimental overall, but that Bun path is the one deploy shape this repo currently supports and tests.