Skip to Main content

Frontend Deployment

This page covers the frontend settings that matter for deployment, what happens after a merge to master, and how to sanity-check the generated static site locally before release.

This guide focuses on the deployment-specific part of the Precise Alloy frontend workflow. If you only need a quick check before release, the local build step near the end is the useful bit: build it once, confirm the output looks sane, and let the pipeline do the repetitive work.

Configuration

Inside the /PreciseAlloy.Frontend/.env.eshn file, set the following values:

  • VITE_BASE_URL
    The base path for serving the Frontend site.
    Should be an absolute path, START and END with /.
    Default value is /. You can change it to something like /static/.

    If you update this value, make sure to apply the same change in /PreciseAlloy.Frontend/.env.development to keep local development and deployment consistent.

  • VITE_PATH_EXTENSION
    Extension for rendered pages output to browsers.
    Should be .html (default) or empty.

  • VITE_TITLE_SUFFIX
    The suffix in the title. For example, if you are on the Home page and the value for this variable is Alloy UI, then the page title will be Home - Alloy UI.

  • NODE_ENV
    It should be set to production mode.

Steps

When frontend changes are pushed to or merged into the master branch, the repository triggers the deployment process and publishes the updated frontend static site.

Local Debugging

To test the deployment build locally, run:

bun run eshn

This command writes the generated site to dist/static. If you want to inspect the result in a browser before the pipeline touches it, serve that directory locally:

bunx serve dist/static