Back to all templates
Wanderer logo

Wanderer

Application512MB+ RAM

Self-hosted trail database — track hiking, running, and cycling routes with maps and GPX

applicationautomationwandereropen-sourceself-hosteddocker

Deploy Wanderer in 3 Steps

1

Connect Your VPS

Add your server credentials to Server Compass

2

Select Wanderer

Choose from our template library

3

Deploy & Configure

Fill in settings and click Deploy

No Docker knowledge required
Step-by-step deployment guide

Deploy Wanderer on a VPS with Server Compass

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.

About 10 minutesBrowser verified
1
Step 1

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.

Server Compass Apps tab before creating a Wanderer app
2
Step 2

Choose an app template

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

Choosing to deploy an app from a Server Compass template
3
Step 3

Search for Wanderer

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

Searching for Wanderer in the Server Compass template picker
4
Step 4

Select the Wanderer template

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

Wanderer template selected in Server Compass
5
Step 5

Review the Wanderer settings

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.

Reviewing Wanderer project settings and compose service
6
Step 6

Deploy Wanderer

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

Reviewing Wanderer web port before deployment
7
Step 7

Watch the deployment progress

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

Server Compass deploying the Wanderer template on the VPS
8
Step 8

Confirm Wanderer is running

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

Wanderer template running in the Server Compass Apps tab
9
Step 9

Open Wanderer in the browser

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

The deployed Wanderer web UI loaded in a browser

After Wanderer Opens

  • Create the first Wanderer account from the web UI; the first registered user becomes the admin.
  • Disable open registration from settings after the intended users have signed up.
  • Upload a sample GPX file or create a test route to verify map rendering and search.
  • Put Wanderer behind HTTPS before storing real location traces or production login sessions.
  • Back up the wanderer_pb_data, wanderer_uploads, and wanderer_search volumes because they store users, trails, uploads, and search indexes.
  • Keep the Wanderer web, PocketBase backend, and Meilisearch images updated for dependency and security fixes.

Verified Result

The Wanderer web UI loaded successfully from the deployed container.

Wanderer deployment questions

What does the Wanderer template deploy?

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.

Which port did the tutorial use?

The tutorial used host port 4226, which maps to the Wanderer web container on port 3000.

Does Wanderer need setup after deployment?

Yes. Open the web UI after deployment, create the first admin account, then configure registration, map providers, user access, and trail upload settings.

Should this become a blog post?

No. The deployment guide should live on the Wanderer template detail page and be linked from the reusable template deployment docs page.

After Deployment

After deploying Wanderer with Server Compass, complete these steps to finish setup

1

Open the application URL and create your account

2

Visit the admin panel and disable open registration

3

Upload a sample GPX trail to verify map rendering works

4

Configure tile providers (OSM, Thunderforest, etc.) in admin settings

5

Invite your team and assign roles

Need help? Check out our documentation for detailed guides.

Wanderer FAQ

Common questions about self-hosting Wanderer

How do I deploy Wanderer with Server Compass?

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.

What are the system requirements for Wanderer?

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.

Can I migrate my existing Wanderer data?

Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Wanderer backup and restore procedures.

How do I update Wanderer to the latest version?

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.

Is Wanderer free to self-host?

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.

Ready to Self-Host Wanderer?

Download Server Compass and deploy Wanderer to your VPS in under 3 minutes. No Docker expertise required.

Download Server Compass