TREK

On first boot, the Seed installs Docker and starts TREK together with Caddy, which accepts HTTPS connections and passes them on to TREK. TREK is reachable 2 to 4 minutes later. You then find the address in /root/ready.txt and your login details in /root/trek-credentials.txt. If /root/failed.txt appears instead, it gives the reason. The complete log is in /root/trek-install.log. As long as neither file exists, the setup is still running. You read these files over SSH or in the Seed's console.

Sign in with the email address from ADMIN_EMAIL and the password from /root/trek-credentials.txt. On your first sign-in you set a password of your own. Under Settings > Account you can later change your email address and turn on two-factor sign-in.

After the installation, registration is closed. Under Admin > Users you create an invite link and pass it on to your travel companions. Anyone with an account can be added to a trip by email address or username. If everyone with the address should be able to register themselves, turn on Password Registration under Admin > Settings. For notifications and forgotten passwords, TREK needs a mail server. Enter its details under Admin > Notifications and check them with a test email.

On your phone, you install TREK as an app from the browser, on iOS through Share > Add to Home Screen and on Android through Menu > Install app. This needs a valid certificate, which the Seed gets from Let's Encrypt with LETSENCRYPT=on. Since all travel companions store the address of TREK on their devices, we recommend using your own domain from the start. Once your domain's A record points to the Seed's IPv4 address, switch TREK over with seed-tls domain trips.example.com via SSH. From then on, invite links use the domain, and the previous address redirects to it. Do this before anyone creates passkeys, because a passkey only works for the address it was created on.

In /opt/trek, compose.yaml defines the containers trek and caddy. The .env file holds the images with their versions, the address of TREK, the time zone and the initial admin password, which TREK reads only on its first start. /opt/trek/data holds the database and the key TREK uses to encrypt stored credentials such as the SMTP password. /opt/trek/uploads holds uploaded files and photos. Include both directories in your backups. Under Admin > Backup you create a ZIP with the database, uploads and key, or let Auto-Backup create one daily. These backups are stored in /opt/trek/data/backups on the same Seed, and each one contains all uploads again. So download them or choose an external target under Admin > Storage. Since the ZIP contains the key, keep it as safe as your credentials.

Before an update, read the TREK release notes and take a snapshot of the Seed. Then replace the entire value of TREK_IMAGE in .env, including the @sha256 part, with the new version, for example docker.io/mauriceboe/trek:5.1.1, and run docker compose pull followed by docker compose up -d in /opt/trek. CADDY_IMAGE updates Caddy the same way. Docker itself updates with apt update && apt upgrade. Both containers start automatically when the Seed reboots.

For place and address search, route calculation and place details, TREK uses its own services, run by the TREK project on servers sponsored by dataforest. Your Seed registers with them on its first search, so there is nothing to set up. TREK asks you as admin once whether it may share the place details your members enter, such as opening hours or phone numbers, with the TREK project. Without your consent, TREK sends none of them, and you can change your choice at any time under Share place details in Admin > Settings.