Deploy the frontend

A step of the Cloud application tree on Gradus, in the Frontend area: Second app, UI, browser tests.

Serve the built frontend behind a CDN from CI on every merge to main, on the same origin as the API or with CORS configured once and properly.

Usually comes after: The first journey in the browser.

Leads to: Browser end-to-end tests, Real 404s & redirects, Cache & compression, Custom domain.

Prompt for your AI assistant

Deploy the frontend from CI on every merge to the main branch: static hosting behind a CDN for a built application, or the service's own deploy for server-rendered HTML. Serve it on the same origin as the API where the platform allows it, otherwise configure CORS on the service for exactly the frontend's origin. Until this product has sign-in, keep the journey's pages and writes behind one shared access code held as a secret, so a stranger cannot write to it. Add a post-deploy check that loads the first page and put the public URL in the README.

This is https://gradus.kazet.blog/tree/cloud-application/step/frontend-deploy as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.