# Demo Operations

This document describes how to operate the public demo deployment.

## What the demo is for

The demo is intended for public browsing and for guided exploration of a pre-seeded instance.

- The default landing page is informational.
- The demo includes seeded communities, proposals, delegations, and moderation history.
- Administrative setup is not part of the public demo experience.

## Services and ports

- Frontend: `http://<host>:4322`
- Backend API: `http://<host>:3001`
- Database: not exposed publicly (bound to localhost in VPS deployments)

## Deploy/update (VPS)

From the VPS, in the repo folder:

- Bring up (or update) the demo:

  - `podman compose --env-file compose/.env.demo -f compose/demo.yml -f compose/demo.vps.override.yml up -d --build`

- Pull latest code before rebuilding:

  - `git pull --ff-only`

## Check health

- Backend health endpoint:
  - `GET /health`

- Check containers:
  - `podman ps`

- Check logs:
  - `podman logs likwid-demo-backend`
  - `podman logs likwid-demo-frontend`
  - `podman logs likwid-demo-db`

## Reset the demo

Resetting is destructive and recreates the demo database.

- `podman compose --env-file compose/.env.demo -f compose/demo.yml -f compose/demo.vps.override.yml down -v`
- `podman compose --env-file compose/.env.demo -f compose/demo.yml -f compose/demo.vps.override.yml up -d --build`

## Security notes

- Keep the database port closed to the public internet.
- Prefer TLS and a reverse proxy once a domain is available.
- Treat demo credentials as public; the demo is not a private environment.