This repository provides a Docker container for SankeyMATIC.
It is a fork of bvmensvoort/docker-sankematic, which is no longer actively maintained.
The container is built automatically via GitHub workflows and hosted on Docker Hub.
- This container is a direct packaging of the original SankeyMATIC repository.
- There are no guarantees for security updates or ongoing maintenance.
- Use at your own risk in production environments.
You can run the container directly via Docker or use Docker Compose for easier configuration.
Below is a sample docker-compose.yml setup:
services:
sankeymatic:
image: docker.io/vectabyte/sankeymatic
container_name: sankeymatic
restart: unless-stopped
networks:
- some-network
ports:
- "8080:80"
volumes:
- ./.apache.conf:/usr/local/apache2/conf/extra/servername.conf
command: /bin/sh -c '(grep -F "Include conf/extra/servername.conf" /usr/local/apache2/conf/httpd.conf > /dev/null || echo "Include conf/extra/servername.conf" >> /usr/local/apache2/conf/httpd.conf) && exec httpd -D FOREGROUND'- This setup mounts a local
.apache.conffile into the container so you can pass a customServerNameto Apache. - Port
8080on the host maps to80in the container.
Create a file named .apache.conf in the same directory as your docker-compose.yml:
ServerName sankeymatic.localhost- This file is automatically included in
httpd.confby the command in Docker Compose. - The container ensures the line is only added if it does not already exist.
- The container runs Apache in the foreground using
httpd -D FOREGROUNDso Docker can manage it correctly. - The included shell command checks for the
Includedirective inhttpd.confand appends it if missing. - Logs can be viewed with:
docker logs -f sankeymatic- The container is built automatically via GitHub workflows.
- Updates to the container only happen when the workflows are triggered.
- This setup is intended for local development and experimentation, not production.