anchorhost-frontend/README.md

AnchorHost.eu frontend

React single-page application for the AnchorHost.eu hosting platform. The app source was recovered from the production image source maps; static runtime assets are in public/assets. The deployed bundle and its maps are retained under recovered-production/ as a reference snapshot.

Development

1. Install Node.js 24 LTS or newer and npm.
2. Run npm ci.
3. Copy .env.example to .env and set the API/WebSocket URLs as needed.
4. Run npm run dev (or npm start).

npm run build creates the production bundle in dist/. The included Dockerfile serves it with nginx and supports client-side routes. Vite expects JSX files to use .jsx; keep .js for plain JavaScript modules.

Rebrand the deployment

Edit the root branding.json to set the product name, domain, logo path, public copy, contact addresses, documentation and source links, and footer credit. Replace the logo file at the configured path under public/. The app imports this file for its UI, API defaults, document metadata, and web app manifest. Keep .env API and WebSocket overrides for deployments whose service endpoints differ from the public brand domain.

Gitea Actions Docker publishing

.gitea/workflows/docker.yml builds the Docker image when main is updated and can also be started manually from the Actions page. It publishes git.anchorhost.eu/anchorhost.eu/anchorhost-frontend:frontend and a commit-specific main-<12 character SHA> tag to the Gitea Container Registry. Add a repository Actions secret named REGISTRY_TOKEN containing a Gitea personal access token with package read/write permission. The workflow uses the triggering Gitea username to authenticate.

Enable Actions for the repository and ensure a runner with the Docker CLI and a working Docker daemon is registered. .dockerignore keeps local dependencies, Git history, build output, and recovered production artifacts out of the build context.