Skip to main content

File Paths

This page lists the most important filesystem paths used by SVRunner during installation, maintenance, backup, and recovery.

Default Server Paths​

In a standard host deployment, the server uses these logical defaults:

  • executable directory: SVR_SERVER_EXEC_DIR
  • persistent data root: SVR_SERVER_FILES_DIR
  • assets directory: SVR_SERVER_ASSETS_DIR
  • logs directory: SVR_SERVER_LOGS_DIR
  • database file: SVR_SERVER_DATABASE_PATH

Default Concrete Layout​

By default, that becomes:

  • <exec-dir>/files/
  • <exec-dir>/files/assets/
  • <exec-dir>/files/logs/
  • <exec-dir>/files/local.db
  • <exec-dir>/.env

Managed Platform Example​

The existing Fly.io deployment notes reference:

  • install path: /usr/src/svrunner
  • runtime data path: /usr/src/svrunner/files

That implies:

  • /usr/src/svrunner/files/assets
  • /usr/src/svrunner/files/logs
  • /usr/src/svrunner/files/local.db

Docker Example​

The root Docker run script currently maps:

$(pwd)/packages/server/files -> /usr/src/svrunner/files

This is the key persistence mount in the documented local container flow.

Kiosk / Player-Side Paths​

The documented Linux kiosk setup uses several important local paths:

  • ~/.xinitrc
  • ~/kiosk.log
  • ~/.vnc/passwd
  • ~/.config/svr-electron-player/settings.json

These matter for remote support and player commissioning.

Maintenance-Relevant Paths​

Admins commonly need these during maintenance:

  • the persistent data root
  • the database file
  • the logs directory
  • the asset library
  • the .env file

Deployment File Paths Stub screenshot: terminal listing of the key paths on one real deployment target, especially the server files/ tree and kiosk config paths if available. Save final image at packages/docs/screenshots/reference-file-paths.png.