Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.


Self-hosted trail database — track hiking, running, and cycling routes with maps and GPX
Add your server credentials to Server Compass
Choose from our template library
Fill in settings and click Deploy
Use the Wanderer template in Server Compass to deploy a self-hosted trail database for hiking, running, cycling routes, maps, and GPX files on your VPS, then verify the web UI in a browser.
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Use the template picker search to find Wanderer in the Server Compass template catalog.

Choose the Wanderer template. Server Compass fills the Wanderer web service, PocketBase backend, Meilisearch service, persistent data volumes, and public web port.

Confirm the app name, Meilisearch key, PocketBase encryption key, persistent Wanderer volumes, and compose services. In this run, the app was named wanderer-demo and used host port 4226.

Review the generated compose settings, confirm the Wanderer web port is available, and click Deploy.

Keep the deployment modal open while Server Compass uploads the compose file, pulls the Wanderer image, starts the container, and verifies the stack.

After deployment finishes, return to the Apps tab and confirm the Wanderer app is marked Running with its application URL available.

Open the application URL in a browser. The Wanderer sign-up, login, or trail dashboard UI confirms the route database is reachable.

The Wanderer web UI loaded successfully from the deployed container.
It deploys Wanderer with a web UI container, a PocketBase backend container, a Meilisearch container, and persistent volumes for trail data, uploads, and search indexes.
The tutorial used host port 4226, which maps to the Wanderer web container on port 3000.
Yes. Open the web UI after deployment, create the first admin account, then configure registration, map providers, user access, and trail upload settings.
No. The deployment guide should live on the Wanderer template detail page and be linked from the reusable template deployment docs page.
After deploying Wanderer with Server Compass, complete these steps to finish setup
Open the application URL and create your account
Visit the admin panel and disable open registration
Upload a sample GPX trail to verify map rendering works
Configure tile providers (OSM, Thunderforest, etc.) in admin settings
Invite your team and assign roles
Need help? Check out our documentation for detailed guides.
Common questions about self-hosting Wanderer
Simply download Server Compass, connect to your VPS, and select Wanderer from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
Wanderer requires a minimum of 512MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Wanderer backup and restore procedures.
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Wanderer image will be pulled and deployed with zero downtime.
Wanderer is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Download Server Compass and deploy Wanderer to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass