Deploy Dawarich
Self-hosted Google Timeline alternative: location history on a map
Redis
Just deployed
/data
Just deployed
/var/app/storage
Just deployed
/var/lib/postgresql/data
Deploy and Host Dawarich on Railway
Dawarich is a self-hosted, open-source alternative to Google Timeline (Location History). It records where you have been from your phone or imports, and shows it on a map with trips, visits, visited countries and cities, and yearly stats. Your location data stays in your own database.
About Hosting Dawarich
This template deploys Dawarich 1.23.0 with everything it needs: the Dawarich web app with its Sidekiq background worker embedded in the same service, PostGIS (PostgreSQL 17 with PostGIS 3.7) and Redis. Each service builds or runs from a pinned version and keeps its data on its own Railway volume. You only enter the email of the first admin. On the first boot Dawarich waits for PostGIS, runs its migrations, creates your admin account with a generated password and loads country and time-zone data, which takes about two minutes. After that, sign in on the public URL and connect a tracking app.
Common Use Cases
- Keep a private, long-term record of your location history instead of Google Timeline
- Import Google Takeout, GPX, GeoJSON or OwnTracks history and explore it on a map
- Track trips and visits live from your phone with the Dawarich, OwnTracks or Overland apps
Dependencies for Dawarich Hosting
- PostgreSQL with PostGIS (included, PostgreSQL 17 + PostGIS 3.7)
- Redis (included, Railway's Redis)
Deployment Dependencies
- Dawarich source and releases: https://github.com/Freika/dawarich/releases
- Dawarich self-hosting docs: https://dawarich.app/docs/intro
- Environment variables: https://dawarich.app/docs/self-hosting/environment-variables/
- Template repository: https://github.com/aalfath/dawarich-railway-template
Implementation Details
Services in this template:
- Dawarich: the Rails web app on the public domain, with Sidekiq embedded for imports, reverse geocoding and stats. Health check
/api/v1/health. Uploads and exports live on a volume at/var/app/storage. - PostGIS: PostgreSQL 17 with PostGIS, private network only, data on a volume.
- Redis: job queue and cache, private network only, data on a volume.
After deploy:
- Open the Dawarich service's Variables tab and copy
DAWARICH_ADMIN_PASSWORD. - Sign in at your Railway URL with
DAWARICH_ADMIN_EMAILand that password, then change the password in your account settings. - Find your API key in Settings and use it in the Dawarich iOS app, OwnTracks or Overland, or import your history under Imports.
The upstream demo account with a fixed password is never created, and public sign-up stays off: the admin adds other users under Settings → Users. For a custom domain, add it to APPLICATION_HOSTS on the Dawarich service (comma separated). SMTP, OIDC sign-in and other options are optional variables described in the Dawarich environment variable docs.
Updates: every service builds from the template's GitHub repository. When a new Dawarich version is released there, Railway shows an "update available" notice and you choose when to apply it. Read the repository's CHANGELOG first, and back up the PostGIS volume before large version jumps, because Dawarich migrates its database on start.
Why Deploy Dawarich on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Dawarich on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Redis
redis:8.2DAWARICH_ADMIN_EMAIL
Email for the first admin account, created on first boot. You sign in with it.
