wanderer - Self-Hosted Trail and GPS Route Database

AWS Application Stacks
Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Pre-hardened wanderer to browse, upload and map hiking, cycling and running trails, with unique credentials per instance and dedicated storage. Ready in minutes with 24/7 cloudimg support.

Why the cloudimg image

This image arrives installed, configured and hardened, so there is no manual setup before you can use it. It is built on a patched base, runs with credentials generated uniquely for your instance on first boot, and passes an automated health check before every release. Every deployment is backed by 24/7 support from cloudimg engineers.

Key features

  • Prebuilt and secure in minutes: a multi-service application - web frontend, backend database and authentication layer, and full-text search engine - normally wired together by hand with container orchestration, a reverse proxy and shared secrets, delivered fully assembled and hardened. Launch an instance and reach a working trail and GPS-route database without editing a single configuration file.
  • Secure by default with unique per-instance credentials: the search engine master key and backend encryption key are generated on first boot, a backend administrator and a first application user are seeded with cryptographically random per-instance passwords, open sign-up is disabled by default, the search engine and backend are never network-exposed, and the admin console is reachable only over an authenticated SSH tunnel - no two deployments share a secret.
  • Full trail database with dedicated storage and 24/7 support: upload GPX tracks, plan hiking, cycling and running routes on an interactive map, add waypoints, photos, lists and statistics, and search the whole catalogue from the browser. The database, uploads and search index live on a dedicated independently resizable data volume. Backed by 24/7 cloudimg technical support via email and chat.

See it running

Real screenshots taken while testing this image against its deployment guide.

wanderer - Self-Hosted Trail and GPS Route Database screenshot 1 wanderer - Self-Hosted Trail and GPS Route Database screenshot 2 wanderer - Self-Hosted Trail and GPS Route Database screenshot 3 wanderer - Self-Hosted Trail and GPS Route Database screenshot 4

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Overview

wanderer is a free and open-source self-hosted trail and GPS-route database. Upload your GPX tracks, plan and organise hiking, cycling and running routes on an interactive map, and keep everything - waypoints, photos, lists and statistics - in a private instance you run and control in your own AWS account. This AMI delivers wanderer fully installed and secured, so a working trail database is operational within minutes of launch.

## Why This Image vs a Manual Install

wanderer is a multi-service application: a web frontend, a backend built on an embedded database and authentication layer, and a full-text search engine, normally wired together by hand with container orchestration, a reverse proxy and a set of shared secrets. This image completes all of that at build time. It runs the official upstream releases unmodified, pinned by digest, behind a single reverse proxy, and generates every secret uniquely on each instance's first boot. Launch the instance, read your unique credential, and start mapping trails.

## Application Stack

The web frontend, the backend database and authentication service, and the full-text search engine each run as their own service, orchestrated on a private internal network and fronted by a single reverse proxy on port 80. The search engine and the backend admin interface are never exposed to the network: the search engine has no host port at all, and the backend is reachable only over the loopback interface for an administrator's SSH tunnel. systemd starts the whole stack on boot. All application data - the database, uploaded GPX tracks and photos, and the search index - lives on a dedicated data volume, independently resizable and separate from the OS disk.

## Security Hardening

This image follows a defence-in-depth approach:

  • No default, shared or blank credentials: the search engine master key and the backend encryption key are generated uniquely on each instance's first boot, and a backend administrator account plus a first application user are seeded with cryptographically random per-instance passwords written only to a root-only file
  • Network isolation: the search engine is never published to any host port; the backend binds to the loopback interface only; only the reverse proxy on port 80 is reachable
  • Admin interface not public: the backend administration console is blocked at the proxy and reachable only through an authenticated SSH tunnel
  • Registration closed by default: open self-service sign-up is disabled so a fresh public instance is not world-joinable, and can be enabled by the operator when wanted
  • Dedicated data volume: the database, uploads and search index live on their own disk, surviving OS-disk changes and resizable independently
  • Automatic restart: systemd supervises the whole stack and restarts it on failure

Buyers requiring formal compliance documentation should contact cloudimg to discuss specific requirements.

## Concrete Use Cases

  • Hiking and outdoor clubs: a private, self-hosted catalogue of the group's routes with GPX tracks, photos and waypoints, organised into shareable lists on an interactive map
  • Cycling and running training logs: athletes and coaches recording and reviewing sessions with elevation profiles and per-route statistics in an instance they fully own
  • Field and survey teams: organisations that must keep location and route data inside their own account, uploading GPX from handheld devices and browsing it on a map without sending it to a third-party service

## AWS Integration

Deploy on any EC2 instance type. Put the reverse proxy behind an Application Load Balancer and terminate TLS with your own domain and certificate. Back up your database, uploads and search index using EBS snapshots or AWS Backup of the dedicated data volume, which you can resize independently of the OS disk as your trail library grows.

## Getting Started

Read your credential from the root-only file, open the web interface in your browser, sign in with the seeded application account, and upload your first GPX track or draw a route on the map. Organise trails into lists, add waypoints and photos, and search your whole catalogue. Interactive map display, trail upload, browsing and search work out of the box against the public OpenStreetMap map, geocoding and routing services; self-hosting the optional turn-by-turn routing tiles is covered in the user guide.

## cloudimg Support

24/7 technical support by email and chat. Help with deployment, reverse-proxy termination with your own domain and certificate, backend administration, enabling open registration, self-hosting the optional routing service, and backup planning for your trail database.

Related technologies

wanderergpxhikingtrailgps routeself-hostedcyclingrunningoutdoormap