|Dryusdan 54932a16cb autoupdate||2 years ago|
|rootfs||2 years ago|
|.drone.yml||2 years ago|
|Dockerfile||2 years ago|
|README.md||2 years ago|
|lastAutoupdate||2 years ago|
It is a web analytics platform. Piwik respects your privacy and gives you full control over your data.
Piwik can update itself. It works well. I'm also maintaing this Dockerfile, so if you don't want to do upgrades directly from Piwik, you can recreate the container as well whenever I push an update.
According to Piwik, everything should be fine running this image. You shoudn't have any difficulties to setup your own instance of Piwik. Your
/config/config.ini.php overwrites the one (in
/piwik/config)used by Piwik each time the container is started. Moreover, the old config.ini.php is saved as
/config/config.ini.php.bkp if you want to revert last changes. This should also guarantee transparency through Piwik's updates.
If you're running Piwik behind a reverse proxy (most likely you do), add this to your
[General] #assume_secure_protocol = 1 #uncomment if you use https proxy_client_headers = HTTP_X_FORWARDED_FOR proxy_client_headers = HTTP_X_REAL_IP proxy_host_headers = HTTP_X_FORWARDED_HOST
piwik: image: wonderfall/piwik links: - db_piwik:db_piwik volumes: - /mnt/docker/piwik/config:/config environment: - GID=1000 - UID=1000 db_piwik: image: mariadb:10 volumes: - /mnt/docker/piwik/db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD=asupersecretpassword - MYSQL_DATABASE=piwik - MYSQL_USER=piwik - MYSQL_PASSWORD=asupersecretpassword