![Pumperly]()
Pumperly
Stack
Open-source fuel and EV route planner with real-time prices across 36 countries. Source: https://github.com/GeiserX/Pumperly
Source details
Notes
Services
pumperly
Configuration
Imagedrumsergio/pumperly:latest3000:3000DATABASE_URL=postgresql://pumperly:pumperly@postgres:5432/pumperlyTZ=UTCPUMPERLY_DEFAULT_COUNTRY=${PUMPERLY_DEFAULT_COUNTRY:-ES}PUMPERLY_CLUSTER_STATIONS=truePUMPERLY_EV_ENABLED=1unless-stoppedImage details
postgres
Configuration
Imagepostgis/postgis:17-3.4/var/lib/postgresql/data : postgres-dataPOSTGRES_DB=pumperlyPOSTGRES_USER=pumperlyPOSTGRES_PASSWORD=pumperlyunless-stoppedImage details
Standalone Install
Select an install method, to see config/commands for deploying Pumperly
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 Pumperly, 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:
services:
pumperly:
image: drumsergio/pumperly:latest
restart: unless-stopped
ports:
- "3000:3000"
environment:
- DATABASE_URL=postgresql://pumperly:pumperly@postgres:5432/pumperly
- TZ=UTC
- PUMPERLY_DEFAULT_COUNTRY=${PUMPERLY_DEFAULT_COUNTRY:-ES}
- PUMPERLY_CLUSTER_STATIONS=true
- PUMPERLY_EV_ENABLED=1
# Optional external services — uncomment and point at your own instances:
# - VALHALLA_URL=http://valhalla:8002 # enables route planning
# - PHOTON_URL=http://photon:2322 # enables address autocomplete / geocoding
# - PUMPERLY_OCM_API_KEY= # OpenChargeMap key for EV charging data
depends_on:
- postgres
deploy:
resources:
limits:
memory: 512M
postgres:
image: postgis/postgis:17-3.4
restart: unless-stopped
environment:
- POSTGRES_DB=pumperly
- POSTGRES_USER=pumperly
- POSTGRES_PASSWORD=pumperly
volumes:
- postgres-data:/var/lib/postgresql/data
volumes:
postgres-data:
Or deploy it directly from the source:
git clone https://github.com/lissy93/portainer-templates
cd portainer-templates
docker compose -f sources/stacks/pumperly.yml up -dMore install options in our documentation, or see GeiserX/Pumperly for app-specific guidance.
Container Documentation
pumperly Documentation
postgres Documentation
PostGIS is a spatial database extender for PostgreSQL object-relational database.
Serve Pumperly 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 pumperly.example.com to http://pumperly:3000
Add this to your Caddyfile
pumperly.example.com {
reverse_proxy http://pumperly: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, pumperly can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 3000
Image won't pull
Test the pull directly on the host: docker pull drumsergio/pumperly:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "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 unless-stopped 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 on GeiserX/Pumperly
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Pumperly is a Compose stack, a set of containers (2 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 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
pumperlyrunsdrumsergio/pumperly:latest, starts after postgrespostgresrunspostgis/postgis:17-3.4
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 Pumperly 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:
/var/lib/postgresql/datakept in thepostgres-datavolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Pumperly takes 8 of them, all with defaults you can leave alone or tweak:
DATABASE_URL, defaults topostgresql://pumperly:pumperly@postgres:5432/pumperlyTZ, defaults toUTCPUMPERLY_DEFAULT_COUNTRY, defaults toESPUMPERLY_CLUSTER_STATIONS, defaults totruePUMPERLY_EV_ENABLED, defaults to1POSTGRES_DB, defaults topumperlyPOSTGRES_USER, defaults topumperlyPOSTGRES_PASSWORD, defaults topumperly
Restart policy
The restart policy here is unless-stopped, so Docker restarts Pumperly after a crash or reboot, but leaves it off when you stop it on purpose. 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 pumperly) 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.
Open source license
Pumperly is open source, released under the GPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Pumperly up. Add the template list to Portainer once, then deploying Pumperly is a click rather than a wall of config.