Skip to content
SuperDOCS

Deployment

Production build

Section titled “Production build”
Terminal window
npm run build
npm start

The production API serves the React application from apps/web/dist.

Standalone Docker

Section titled “Standalone Docker”
Terminal window
cp .env.example .env
docker compose up -d --build

The full application is exposed on 4030, with SQLite persisted in the super-es-manager-data volume.

Path-prefix deployment

Section titled “Path-prefix deployment”

The same image can run below /es-manager/ or any nested prefix:

Terminal window
docker compose -f docker-compose.yml -f docker-compose.subpath.yml up -d --build

The reverse proxy must:

  • Strip the external prefix before forwarding.
  • Overwrite rather than append client-supplied X-Forwarded-Prefix.
  • Keep the trailing slash on proxy_pass.
  • Scope cookies with proxy_cookie_path.
  • Avoid a fixed VITE_PUBLIC_BASE.

Persistence

Section titled “Persistence”

Use SQLite for local deployments or PostgreSQL, MySQL, or MariaDB for shared production environments. Back up and monitor both the database and transfer storage.