Astro Static Deployment on cPanel

Build and public output

1. Install reproducible dependencies with npm ci, then run the candidate checks and npm run build.
2. Inspect generated HTML, assets and allowlisted API files in dist/.
3. Publish the public output to the intended document root. Never upload secrets, sessions, logs or configuration backups as public assets.

Runtime prerequisites

Astro pages are static HTML. Functional Contact and Overmind additionally require same-origin PHP 8.2+ Apache with cURL and honored API access restrictions. Static-only hosting or Astro preview cannot execute these PHP APIs. Deny direct access to /api/inc/; supply private configuration separately from versioned public output and use private durable storage outside served files and the checkout.

Contact uses /api/contact.php, token bootstrap and a visible reCAPTCHA v2 checkbox. PHP mail acceptance is distinct from actual inbox delivery. Overmind uses /api/overmind.php and requires a compatible authenticated v2 service on the configured loopback host. Browser code does not prove any model, RAG or external service is running.

Deployment evidence

Record the published source version, target, date, environment, exact checks and limitations. Verify HTTPS/origin, blocked private includes, CAPTCHA, cookies/storage, mail delivery and upstream compatibility separately. A local build, mock test or historical validation is not evidence of current deployment. Replace public files with the identified candidate while preserving private hosting configuration.