Skip to content

Commit

Permalink
No longer use volume for Matomo install
Browse files Browse the repository at this point in the history
Having the code base in a volume makes upgrades and migrations a pain,
additionaly the file copies on initial startup can be really slow on NFS
drives.

Having a volume allows for the dynamic installation of plugins, but then
that is specific to that instance, if you were to run a several stage
environment dev/stage/prod then one would need to manually check that
the plugins exist is each environment. Better would be to extend the
image and pack the plugins in with the installation.

@see matomo-org/docker#57
@see matomo-org/docker#161
  • Loading branch information
nigelgbanks authored and Nigel Banks committed Mar 23, 2022
1 parent 4d10ef5 commit eb233ab
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 12 deletions.
2 changes: 1 addition & 1 deletion matomo/Dockerfile
Expand Up @@ -36,7 +36,7 @@ ENV \
MATOMO_USER_NAME=admin \
MATOMO_USER_PASS='$2y$10$S38e7HPM9LI3aOIvcnRsfuMCm4ipNP572QsvbCK60upoHVJ61hMrS'

COPY --from=download --chown=nginx:nginx /opt/matomo /opt/matomo
COPY --from=download --chown=nginx:nginx /opt/matomo /var/www/matomo

COPY rootfs /

Expand Down
11 changes: 0 additions & 11 deletions matomo/rootfs/etc/cont-init.d/00-matomo-deploy.sh

This file was deleted.

0 comments on commit eb233ab

Please sign in to comment.