Inconvenient setup, even harder upgrades

[Richie765]

I guess others have already pointed out that the setup is quite hard. Having to setup a separate nginx just to handle the fastcgi, plus a third container just for a simple cron.

There is an even bigger downside to this. Since the piwik codebase has to be shared between the nginx container and the piwik container, a volume is defined:

VOLUME /var/www/html

This will put the piwik code into a volume.

The problem is, when an update comes out, this volume will not be replaced and you'll just run a newer container with the code from the old one. To upgrade, one has to manually delete the volume and container, hoping that the configuration is kept in tact.

I think it would be much better to include everything into one image, including the cron, making installation and upgrading easy as we've come to expect from Docker.

Is there a reason why it is setup like this? Perhaps I'm overlooking something?

[ibotty]

Plugins get installed into the shared volume, and afaict there is no "install all required plugins" step on container startup. So having an ephemeral volume would not work (atm).

If you know what parts have to be stored on a shared volume and which should not, I would contribute to make upgrade smoother.

I personally like a setup that uses two containers (and a cron job, somewhere) though.

[sebastienvermeille]

I personally like a setup that uses two containers (and a cron job, somewhere) though.

It's a point of view I can understand. But I would prefere an AIO container too. I don't really care if they use apache2, nginx or something else I just want something working out of the box which can get updated without loosing any data. (External db).

I will try to do a docker image to achieve that. Would be a good exercice for me.

[crazy-max]

I have created a Docker image here with advanced features like a cron to archive Matomo reports and update GeoLite data, SSMTP for SMTP relay to send emails. It is based on Alpine 3.7 with Nginx (+ GeoIP HTTP module enabled). I have also added a docker-compose.yml with Nginx proxy + Let's Encrypt and some instructions to use Redis for caching. Hope that's help.

[juliencarnot]

PR#52 has added an apache version (see #47 for discussion) and the Matomo docker hub page now includes info on how to run PHP-FPM with docker compose, shall we close this issue?

[J0WI]

I'm closing this. The main part of this issue has already been fixed an the update issue is the same as #161.