![Medama]()
Medama
Stack
Medama Analytics is an open-source project dedicated to providing self-hostable, cookie-free website analytics.
Image details
Source details
Configuration
TypeComposelinuxghcr.io/medama-io/medama:latest8010:8080/app/data : /portainer/Files/AppData/Config/medamaStandalone Install
Select an install method, to see config/commands for deploying Medama
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 Medama, 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:
medama:
image: ghcr.io/medama-io/medama:latest
ports:
- "8010:8080"
volumes:
- /portainer/Files/AppData/Config/medama:/app/data
volumes:
medama-data:
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/medama.yml up -dMore install options in our documentation, or see medama-io/medama for app-specific guidance.
<source media="(prefers-color-scheme: dark)" srcset="./.github/images/banner-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="./.github/images/banner-light.svg">
<img alt="Medama: Cookie-free privacy-focused website analytics." src="https://raw.githubusercontent.com/medama-io/medama/HEAD/.github/images/banner-light.svg">
Website |
Installation |
Demo |
Discord
Overview
Medama Analytics is an open-source project dedicated to providing self-hostable, cookie-free website analytics. With a lightweight tracker of less than 1KB, it aims to offer useful analytics while prioritising user privacy.<a href="https://demo.medama.io" target="_blank">
<img src="https://raw.githubusercontent.com/medama-io/medama/HEAD/.github/images/demo.png" alt="Demo Screenshot" width="70%" height="70%">
</a>Features
- 📊 Real-Time Analytics: Monitor website performance and user interactions instantly.
- 🔒 Privacy-Focused: Lightweight tracker (<1KB) without cookies, IP addresses, or additional identifiers, ensuring compliance with GDPR, PECR, and other regulations.
- 🧪 Easy To Integrate: OpenAPI-based server for effortless integration into personal or professional dashboards.
- 💼 Self-Hostable: Simple, single-binary setup with no external dependencies, capable of running on VMs with 256MB memory for most small websites.
License
The/core and /dashboard directory is licensed under the Apache License 2.0. See the core LICENSE and dashboard LICENSE for more information.The
/tracker directory is licensed under the MIT License. See LICENSE for more information.Serve Medama 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 medama.example.com to http://medama:8080
Add this to your Caddyfile
medama.example.com {
reverse_proxy http://medama:8080
}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:8010 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8010 - Stop the other service, or pick a different host port. In
8010:8080only 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:8010. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, medama can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8010
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/medama
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/medama-io/medama: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.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
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 medama-io/medama
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Medama is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.
The app image
An image is the app packed up ready to go, everything Medama needs bundled into one download. This template pulls ghcr.io/medama-io/medama:latest, which Docker fetches once (about 37 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Medama's comes from the GitHub Container Registry, published by medama-io.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 8010:8080 means it's reachable on port 8010 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:8010 in a browser. It opens:
8010:8080, likely the web interface
Volumes
A volume is where Medama 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:
/app/datafrom/portainer/Files/AppData/Config/medamaon the host
Networking
Nothing custom is set, so Medama sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container medama. That's what you'll spot in the containers list and use in commands like docker logs medama.
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 Medama up. Add the template list to Portainer once, then deploying Medama is a click rather than a wall of config.