What's already set up
The one-click deploy brings up the mauriceboe/trek Docker container with Node.js/Express serving the app on port 3000 internally, backed by a SQLite database that's created automatically at /app/data/travel.db on first boot, plus an /app/uploads volume for attached documents and images. Health checks against /api/health and container restart policy (unless-stopped) are configured out of the box, so the process comes back up after a host reboot without manual intervention.
The at-rest ENCRYPTION_KEY used to protect stored secrets (API keys, MFA, SMTP, OIDC credentials) is auto-generated on first start unless one is supplied.
First login
Trek has no default admin account — the first person to open the instance's URL and complete the registration form becomes the administrator automatically. From there, the Admin Panel (visible in the top navigation once logged in) is where you manage users, invite links, packing templates, and optional integrations like Google Places or an OIDC provider.
Backups and updates
Auto-backups can be scheduled from the Admin Panel with a configurable interval and retention, storing snapshots alongside the SQLite database; restoring one is also done from that same panel. Because Trek doesn't self-update, new versions are pulled manually with a Docker Compose command.








