Dawarich
Stack
Self-Hosted Location History Tracker. | Visualize your location history, track your movements, and analyze your travel patterns with complete privacy and control.
Services
dawarich_redis
Configuration
Imageredis:7.0-alpineredis-server/data : /portainer/Files/AppData/Config/dawarich/sharedalwaysImage details
dawarich_db
Configuration
Imagepostgis/postgis:17-3.5-alpine/var/lib/postgresql/data : /portainer/Files/AppData/Config/dawarich/dawarich_db_data/var/shared : /portainer/Files/AppData/Config/dawarich/sharedPOSTGRES_USER=postgresPOSTGRES_PASSWORD=passwordalwaysImage details
dawarich_app
Configuration
Imagefreikin/dawarich:latestbin/rails,server,-p,3000,-b,::web-entrypoint.sh3000:3000/var/app/public : /portainer/Files/AppData/Config/dawarich/public/var/app/tmp/imports/watched : /portainer/Files/AppData/Config/dawarich/watched/var/app/storage : /portainer/Files/AppData/Config/dawarich/storageRAILS_ENV=developmentREDIS_URL=redis://dawarich_redis:6379/0DATABASE_HOST=dawarich_dbDATABASE_USERNAME=postgresDATABASE_PASSWORD=passwordDATABASE_NAME=dawarich_developmentMIN_MINUTES_SPENT_IN_CITY=60APPLICATION_HOSTS=localhostTIME_ZONE=Europe/AthensAPPLICATION_PROTOCOL=httpDISTANCE_UNIT=kmPROMETHEUS_EXPORTER_ENABLED=falsePROMETHEUS_EXPORTER_HOST=0.0.0.0PROMETHEUS_EXPORTER_PORT=9394SELF_HOSTED=trueon-failureImage details
dawarich_sidekiq
Configuration
Imagefreikin/dawarich:latestsidekiqsidekiq-entrypoint.sh/var/app/public : /portainer/Files/AppData/Config/dawarich/public/var/app/tmp/imports/watched : /portainer/Files/AppData/Config/dawarich/watched/var/app/storage : /portainer/Files/AppData/Config/dawarich/storageRAILS_ENV=developmentREDIS_URL=redis://dawarich_redis:6379/0DATABASE_HOST=dawarich_dbDATABASE_USERNAME=postgresDATABASE_PASSWORD=passwordDATABASE_NAME=dawarich_developmentAPPLICATION_HOSTS=localhostBACKGROUND_PROCESSING_CONCURRENCY=10APPLICATION_PROTOCOL=httpDISTANCE_UNIT=kmPROMETHEUS_EXPORTER_ENABLED=falsePROMETHEUS_EXPORTER_HOST=dawarich_appPROMETHEUS_EXPORTER_PORT=9394SELF_HOSTED=trueon-failureImage details
Standalone Install
Select an install method, to see config/commands for deploying Dawarich
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Dawarich, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
networks:
dawarich:
services:
dawarich_redis:
image: redis:7.0-alpine
container_name: dawarich_redis
command: redis-server
networks:
- dawarich
volumes:
- /portainer/Files/AppData/Config/dawarich/shared:/data
restart: always
healthcheck:
test: [ "CMD", "redis-cli", "--raw", "incr", "ping" ]
interval: 10s
retries: 5
start_period: 30s
timeout: 10s
dawarich_db:
image: postgis/postgis:17-3.5-alpine
shm_size: 1G
container_name: dawarich_db
volumes:
- /portainer/Files/AppData/Config/dawarich/dawarich_db_data:/var/lib/postgresql/data
- /portainer/Files/AppData/Config/dawarich/shared:/var/shared
# - ./postgresql.conf:/etc/postgresql/postgresql.conf # Optional, uncomment if you want to use a custom config
networks:
- dawarich
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: password
restart: always
healthcheck:
test: [ "CMD-SHELL", "pg_isready -U postgres -d dawarich_development" ]
interval: 10s
retries: 5
start_period: 30s
timeout: 10s
# command: postgres -c config_file=/etc/postgresql/postgresql.conf # Use custom config, uncomment if you want to use a custom config
dawarich_app:
image: freikin/dawarich:latest
container_name: dawarich_app
volumes:
- /portainer/Files/AppData/Config/dawarich/public:/var/app/public
- /portainer/Files/AppData/Config/dawarich/watched:/var/app/tmp/imports/watched
- /portainer/Files/AppData/Config/dawarich/storage:/var/app/storage
networks:
- dawarich
ports:
- 3000:3000
# - 9394:9394 # Prometheus exporter, uncomment if needed
stdin_open: true
tty: true
entrypoint: web-entrypoint.sh
command: ['bin/rails', 'server', '-p', '3000', '-b', '::']
restart: on-failure
environment:
RAILS_ENV: development
REDIS_URL: redis://dawarich_redis:6379/0
DATABASE_HOST: dawarich_db
DATABASE_USERNAME: postgres
DATABASE_PASSWORD: password
DATABASE_NAME: dawarich_development
MIN_MINUTES_SPENT_IN_CITY: 60
APPLICATION_HOSTS: localhost
TIME_ZONE: Europe/Athens
APPLICATION_PROTOCOL: http
DISTANCE_UNIT: km
PROMETHEUS_EXPORTER_ENABLED: false
PROMETHEUS_EXPORTER_HOST: 0.0.0.0
PROMETHEUS_EXPORTER_PORT: 9394
SELF_HOSTED: "true"
logging:
driver: "json-file"
options:
max-size: "100m"
max-file: "5"
healthcheck:
test: [ "CMD-SHELL", "wget -qO - http://127.0.0.1:3000/api/v1/health | grep -q '\"status\"\\s*:\\s*\"ok\"'" ]
interval: 10s
retries: 30
start_period: 30s
timeout: 10s
depends_on:
dawarich_db:
condition: service_healthy
restart: true
dawarich_redis:
condition: service_healthy
restart: true
deploy:
resources:
limits:
cpus: '0.50' # Limit CPU usage to 50% of one core
memory: '4G' # Limit memory usage to 4GB
dawarich_sidekiq:
image: freikin/dawarich:latest
container_name: dawarich_sidekiq
volumes:
- /portainer/Files/AppData/Config/dawarich/public:/var/app/public
- /portainer/Files/AppData/Config/dawarich/watched:/var/app/tmp/imports/watched
- /portainer/Files/AppData/Config/dawarich/storage:/var/app/storage
networks:
- dawarich
stdin_open: true
tty: true
entrypoint: sidekiq-entrypoint.sh
command: ['sidekiq']
restart: on-failure
environment:
RAILS_ENV: development
REDIS_URL: redis://dawarich_redis:6379/0
DATABASE_HOST: dawarich_db
DATABASE_USERNAME: postgres
DATABASE_PASSWORD: password
DATABASE_NAME: dawarich_development
APPLICATION_HOSTS: localhost
BACKGROUND_PROCESSING_CONCURRENCY: 10
APPLICATION_PROTOCOL: http
DISTANCE_UNIT: km
PROMETHEUS_EXPORTER_ENABLED: false
PROMETHEUS_EXPORTER_HOST: dawarich_app
PROMETHEUS_EXPORTER_PORT: 9394
SELF_HOSTED: "true"
logging:
driver: "json-file"
options:
max-size: "100m"
max-file: "5"
healthcheck:
test: [ "CMD-SHELL", "bundle exec sidekiqmon processes | grep $${HOSTNAME}" ]
interval: 10s
retries: 30
start_period: 30s
timeout: 10s
depends_on:
dawarich_db:
condition: service_healthy
restart: true
dawarich_redis:
condition: service_healthy
restart: true
dawarich_app:
condition: service_healthy
restart: true
deploy:
resources:
limits:
cpus: '0.50' # Limit CPU usage to 50% of one core
memory: '4G' # Limit memory usage to 4GB
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/dawarich.yml up -dMore install options in our documentation.
Container Documentation
dawarich_redis Documentation
Redis is the world’s fastest data platform for caching, vector search, and NoSQL databases.
dawarich_db Documentation
PostGIS is a spatial database extender for PostgreSQL object-relational database.
Serve Dawarich on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying dawarich.example.com to http://dawarich_app:3000
Add this to your Caddyfile
dawarich.example.com {
reverse_proxy http://dawarich_app:3000
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:3000 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :3000 - Stop the other service, or pick a different host port. In
3000:3000only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:3000. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, dawarich can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 3000
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/dawarich/shared(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull redis:7.0-alpine
- "manifest unknown" means the tag no longer exists.
- "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The always restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within dawarich's repo
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Dawarich is a Compose stack, a set of containers (4 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 4 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
dawarich_redisrunsredis:7.0-alpinedawarich_dbrunspostgis/postgis:17-3.5-alpinedawarich_apprunsfreikin/dawarich:latest, starts after dawarich_db, dawarich_redisdawarich_sidekiqrunsfreikin/dawarich:latest, starts after dawarich_db, dawarich_redis, dawarich_app
Ports
A port is the door the app answers on. A mapping like 3000:3000 means it's reachable on port 3000 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:3000 in a browser. It opens:
3000:3000, likely the web interface
Volumes
A volume is where Dawarich keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/datafrom/portainer/Files/AppData/Config/dawarich/sharedon the host/var/lib/postgresql/datafrom/portainer/Files/AppData/Config/dawarich/dawarich_db_dataon the host/var/sharedfrom/portainer/Files/AppData/Config/dawarich/sharedon the host/var/app/publicfrom/portainer/Files/AppData/Config/dawarich/publicon the host/var/app/tmp/imports/watchedfrom/portainer/Files/AppData/Config/dawarich/watchedon the host/var/app/storagefrom/portainer/Files/AppData/Config/dawarich/storageon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Dawarich takes 18 of them, all with defaults you can leave alone or tweak:
POSTGRES_USER, defaults topostgresPOSTGRES_PASSWORD, defaults topasswordRAILS_ENV, defaults todevelopmentREDIS_URL, defaults toredis://dawarich_redis:6379/0DATABASE_HOST, defaults todawarich_dbDATABASE_USERNAME, defaults topostgresDATABASE_PASSWORD, defaults topasswordDATABASE_NAME, defaults todawarich_developmentMIN_MINUTES_SPENT_IN_CITY, defaults to60APPLICATION_HOSTS, defaults tolocalhostTIME_ZONE, defaults toEurope/AthensAPPLICATION_PROTOCOL, defaults tohttpDISTANCE_UNIT, defaults tokmPROMETHEUS_EXPORTER_ENABLED, defaults tofalsePROMETHEUS_EXPORTER_HOST, defaults todawarich_appPROMETHEUS_EXPORTER_PORT, defaults to9394SELF_HOSTED, defaults totrueBACKGROUND_PROCESSING_CONCURRENCY, defaults to10
Restart policy
The restart policy here is always, so Docker brings Dawarich back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Portainer puts these services on one shared private network, so they can find each other by name (like dawarich_redis) while only the ports above are open to you.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Dawarich up. Add the template list to Portainer once, then deploying Dawarich is a click rather than a wall of config.