# Demo instance for screenshots

The website shows real netOrk screens, taken from a local copy of a production
database with every hostname, domain, address, MAC and name replaced.

```
pg_dump -Fc ... > netork.dump                 # on the production host, by hand
scripts/demo/up.sh restore netork.dump        # fresh local DB + anonymize.py
scripts/demo/up.sh start                      # API :8000, UI http://127.0.0.1:5173
scripts/screenshots/capture.py --list-devices
scripts/screenshots/capture.py --var ap=<id> --var switch=<id> --var server=<id>
```

Log in as `netork` / `netork-demo`.

- Only the API and the UI run. There is no worker, no beat and no Redis, so
  nothing polls or reaches a device. Stored credentials are emptied, and the
  encryption key is random per start.
- The mapping from real to demo names lives outside the repo in
  `~/.config/netork-screenshots/demo-map.json`, because it lists the real names.
  Domains become `example.demo`.
- `anonymize.py` ends with a leak report. Read it before taking screenshots,
  and look at every image before committing it.
- The dump file itself holds production data: keep it out of the repo and
  delete it when done.