# Static App Deployment Workbench 1.0.0 Standalone Linux/systemd static-site deployment kit. Python3.10+, Git, systemd; Nginx and your own TLS certificate for public hosting. No platform subscription needed. Uses commit-bound git archives, complete file hashes, an atomic current symlink, explicit health/readiness/version/served-byte checks, automatic rollback and a separate verification command. Shared state is never deployed or pruned. ## Complete local Linux example 1. Copy this kit to `/opt/static-kit` (readable by the service user). Create a repository with `site/index.html` from example-site and commit it. No generated/runtime state goes in that site folder. 2. Create a dedicated unprivileged service user `staticapp`. Initialize a new service root: `python3 workbench.py init --root /srv/static-sample`. Make root and its releases traversable/readable by staticapp. Deploy administration needs filesystem ownership and permission to restart the named unit; the serving process does not. 3. Install reference/static-sample.service in `/etc/systemd/system/`, review the paths and user, then `systemctl daemon-reload` and `systemctl enable --now static-sample.service`. Before first deployment readiness is intentionally unavailable. 4. Stage exact source: `python3 workbench.py stage --root /srv/static-sample --repo /path/to/repository --commit FULL_40_CHARACTER_COMMIT`. Save the printed release ID. Staging validates the actual archived site, never the uncommitted working tree. 5. Activate: `python3 workbench.py deploy --root /srv/static-sample --release RELEASE_ID --unit static-sample.service --port 8765 --prefix /sample/`. The command exits nonzero on health failure and records rollback evidence in deploy-log. A failed first deployment stops the unit and removes current. A failed update restores the previous release and checks it again. 6. Independently run `python3 workbench.py verify --root /srv/static-sample --unit static-sample.service --port 8765 --prefix /sample/`. Inspect http://127.0.0.1:8765/sample/. For public use add the provided location snippet to your existing TLS Nginx server and validate its configuration before reload. This kit never edits your Nginx configuration or publishes a domain. 7. Deploy a second committed page, then exercise failure with a committed `` entry (admitted source, deliberately fails readiness). The old release must return. Inspect current, live version and deploy-log separately. To intentionally roll back, deploy a previous known-good release ID. No automatic release deletion. Limits: static assets only,1000 archive entries,16MiB per file,64MiB total. Strict CSP permits same-origin assets, no inline scripts/styles; move these into separate files. No backend, package installation, database migration or arbitrary build execution. The bundled origin binds loopback only, has16 handler slots and5-second sockets; use the configured production reverse proxy for TLS/rate limiting. Hashes provide consistency, not an independently signed authenticity guarantee. Protect administrative filesystem access. The receipt's commit identifies archived source; static admission is not a substitute for your application's own tests. Public DNS/TLS acceptance is separate from local origin acceptance. Run `sudo python3 -m unittest discover -s tests -v` in an isolated disposable Linux systemd VM. Tests create uniquely named transient unprivileged services, serve real HTTP, verify update/health-failure rollback, unchanged shared data, tamper refusal and prefix/traversal denial, then stop only their own services. Windows cannot substitute for this acceptance test.