# Deployment plan: contact-form-cms Scope: the web change only. The server module and host configuration are delivered by other sessions. ## Method The existing Gitea pipeline (continuous_integration.yaml). A push to master deploys the test site and ASF test; production only by manual dispatch. Nothing is merged or deployed without Bryan (a test deploy of the feature branch is allowed on request of Bryan or SLP Software - SLS - Main). ## What changes on deploy - Site bundle with the form (lazy chunks), cms-client package, captcha widget chunk, new `frame-src` in the generated server configs (`web/deploy/iis/web.config`, `web/deploy/nginx/*.conf`, regenerated with `pnpm server-config`). - `siteContent.contactForm.enabled` stays `false` in the merge: the site then asks the server nothing and shows the "Binnenkort" gate. ## Server side prerequisites for turning it on (not built here) | Item | Owner | |---|---| | Contact module in the ASF host, `openapi/andreaslopfotografie.v1.json` | SLS Software - CMS | | `Contact__RecipientEmail` (env only), sender in `Email:AllowedFromAddresses`, `Contact:Enabled` + CMS switch, `MinSeconds`, retention 1 year / 30 days spam | AndreaSlopFotografie (host) | | `ForwardedHeaders:KnownProxies` / `ClientPartitionKey` on IIS | AndreaSlopFotografie (host) | | ASF host CSP `frame-src`: global, global0, global1 (`AllowedSiteFrameOrigins__0..2`) | AndreaSlopFotografie (host) | | Recipient address: later from the CMS site settings (CMS-U11, in preparation) with the environment variable as fallback | SLS Software - CMS | | Captcha: verifier configured with the secret; free key only for tests, paid plan before commercial use | Bryan / SLS Software - CMS | ## Rollback Set `siteContent.contactForm.enabled = false` and redeploy (the gate returns, no token request). The server can also close the form (`Contact:Enabled` off answers 404, which keeps the gate). Captcha problems are handled by the form itself (message plus mail button). ## Test deploy steps (on request) 1. Merge or deploy the feature branch to the ASF test site through the pipeline (switch on only if the test host serves the contact endpoint). 2. Run the real-browser check from the build and test instructions against the test host. ## ASF test host (Pi-Main) - Environment file: `/home/gitea-workflow/apps/andreaslopfotografie/test/shared/env`; restart through the systemd user unit `andreaslopfotografie-test`. Details in the SlpSoftware repo, `construction/contact-form/operations/host-config-checklist.md` (read only; owned by SLP Software - SLS - Main). - `ForwardedHeaders:KnownProxies` for ASF test is already `192.168.1.102` (the proxy Pi). - A test deploy of the feature branch and a pull request are NOT requested yet: Bryan has not finished the local ASF test. SLP Software - SLS - Main reports when he wants a test host deploy.