public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/matomo] Release 4.13.3-debian-11-r6 (#24326) 

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 17:49:49 +01:00 committed by GitHub
parent 72bbb0d9bb
commit 67c2b0081f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 43 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
bitnami/matomo/4/debian-11/Dockerfile
View File

@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T16:09:53Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="4.13.3-debian-11-r5" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/matomo" \
org.opencontainers.image.ref.name="4.13.3-debian-11-r6" \
org.opencontainers.image.title="matomo" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="4.13.3"
@ -22,14 +22,14 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages acl ca-certificates cron curl libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libexpat1 libffi7 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhogweed6 libicu67 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.4-2 libldap-common liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpq5 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl1.1 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp6 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 procps rsync zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"php-8.1.16-0-linux-${OS_ARCH}-debian-11" \
"apache-2.4.55-4-linux-${OS_ARCH}-debian-11" \
"mysql-client-10.6.12-0-linux-${OS_ARCH}-debian-11" \
"libphp-8.1.16-0-linux-${OS_ARCH}-debian-11" \
"ini-file-1.4.5-0-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-0-linux-${OS_ARCH}-debian-11" \
"matomo-4.13.3-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"php-8.1.16-1-linux-${OS_ARCH}-debian-11" \
"apache-2.4.55-5-linux-${OS_ARCH}-debian-11" \
"mysql-client-10.6.12-1-linux-${OS_ARCH}-debian-11" \
"libphp-8.1.16-1-linux-${OS_ARCH}-debian-11" \
"ini-file-1.4.5-1-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-1-linux-${OS_ARCH}-debian-11" \
"matomo-4.13.3-2-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

32
bitnami/matomo/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@ -1,58 +1,58 @@
{
"apache": {
"arch": "amd64",
"digest": "6937b37eaae1a0053c097ae04509cf3ccc4d260dd5fe010572753c3e8b22470d",
"digest": "a1afe61b7489ffb908895a02d0ce3b8771005a61489c35bef21101bb87b00a9d",
"distro": "debian-11",
"type": "NAMI",
"version": "2.4.55-4"
"version": "2.4.55-5"
},
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"ini-file": {
"arch": "amd64",
"digest": "d82fb302437effeec0d20f104b35304c46cf295bb3af56ab00d69ad4ffd39eb0",
"digest": "75d5f74f62ca3a476e5ffc01715b197ba18c3b45a85b18fb61cc68e998616119",
"distro": "debian-11",
"type": "NAMI",
"version": "1.4.5-0"
"version": "1.4.5-1"
},
"libphp": {
"arch": "amd64",
"digest": "8d240182cda57e7a1ee29ced829e84c5b7867615e5d42f7f14eef53b4fb19bed",
"digest": "40f8ff7fad078e7349445015793cfe59e47a6590880dd216e0f33739e681cf9d",
"distro": "debian-11",
"type": "NAMI",
"version": "8.1.16-0"
"version": "8.1.16-1"
},
"matomo": {
"arch": "amd64",
"digest": "ff45aafecd19178ac4cbe0d61602448d3c92bc7d4a31a4985807418763aa5227",
"digest": "8485c608ce1425532dd17cc0927f935fe108898497ec82080178c1cbc500e848",
"distro": "debian-11",
"type": "NAMI",
"version": "4.13.3-1"
"version": "4.13.3-2"
},
"mysql-client": {
"arch": "amd64",
"digest": "f1d55c82fe67003513561ab0b4c91f2e7699d4eaaa5d417dc4ed6be50cb4cbed",
"digest": "dbc087bd90a6387956751464da45660229b3e7349b96099805e61dcbc2514853",
"distro": "debian-11",
"type": "NAMI",
"version": "10.6.12-0"
"version": "10.6.12-1"
},
"php": {
"arch": "amd64",
"digest": "cf3db32904b1b7359117477538ab174df76b2f065e5de5495ba223a8f21f40cd",
"digest": "928131776dab0ecb6d22ccc2b0b5f790fa6886419b60f9b4beb489f70dc76342",
"distro": "debian-11",
"type": "NAMI",
"version": "8.1.16-0"
"version": "8.1.16-1"
},
"render-template": {
"arch": "amd64",
"digest": "57c1d857acbb187fcb98f4ba26d138af9d866f59ad38dd443a75c0a6422de994",
"digest": "185e277977366ec222d2bde1a395ffa138ce1a9d3bdf1df20c3e49e8b8f9c68b",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.5-0"
"version": "1.0.5-1"
}
}

30
bitnami/matomo/README.md
View File

@ -97,7 +97,7 @@ If you want to run the application manually instead of using docker-compose, the
bitnami/mariadb:latest
```
3. Create volumes for {{ .Name }} persistence and launch the container
3. Create volumes for Matomo persistence and launch the container
```console
docker volume create --name matomo_data
@ -164,9 +164,9 @@ In this case you need to specify the directories to mount on the run command. Th
bitnami/mariadb:latest
```
*Note:* You need to give the container a name in order to {{ .Name }} to resolve the host
*Note:* You need to give the container a name in order to Matomo to resolve the host
3. Create the {{ .Name }} container with host volumes:
3. Create the Matomo container with host volumes:
```console
docker run -d --name matomo -p 80:80 -p 443:443 \
@ -210,7 +210,7 @@ Restoring a backup is as simple as mounting the backup as volumes in the contain
For the MariaDB database container:
```diff
docker run -d --name mariadb \
$ docker run -d --name mariadb \
...
- --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+ --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
@ -220,7 +220,7 @@ For the MariaDB database container:
For the Matomo container:
```diff
docker run -d --name matomo \
$ docker run -d --name matomo \
...
- --volume /path/to/matomo-persistence:/bitnami/matomo \
+ --volume /path/to/matomo-backups/latest:/bitnami/matomo \
@ -239,8 +239,8 @@ Bitnami provides up-to-date versions of MariaDB and Matomo, including security p
2. Stop your container
* For docker-compose: `docker-compose stop matomo`
* For manual execution: `docker stop matomo`
* For docker-compose: `$ docker-compose stop matomo`
* For manual execution: `$ docker stop matomo`
3. Take a snapshot of the application state
@ -254,13 +254,13 @@ Bitnami provides up-to-date versions of MariaDB and Matomo, including security p
4. Remove the currently running container
* For docker-compose: `docker-compose rm -v matomo`
* For manual execution: `docker rm -v matomo`
* For docker-compose: `$ docker-compose rm -v matomo`
* For manual execution: `$ docker rm -v matomo`
5. Run the new image
* For docker-compose: `docker-compose up matomo`
* For manual execution mount the directories if needed): `docker run --name matomo bitnami/matomo:latest`
* For docker-compose: `$ docker-compose up matomo`
* For manual execution (mount the directories if needed): `docker run --name matomo bitnami/matomo:latest`
## Configuration
@ -297,7 +297,7 @@ If you are connecting through a reverse proxy (https-to-http) and Matomo is not
* `MATOMO_PROXY_CLIENT_HEADER`: Specify the client IP HTTP Header. Usually 'HTTP_X_FORWARDED_FOR'. No defaults.
* `MATOMO_PROXY_HOST_HEADER`: Specify the host IP HTTP Header. Usually 'HTTP_X_FORWARDED_HOST'. No defaults.
##### Example
##### Reverse proxy configuration example
This would be an example of reverse proxy configuration:
@ -316,7 +316,7 @@ This would be an example of reverse proxy configuration:
* For manual execution:
```console
docker run -d --name matomo -p 80:80 -p 443:443 \
$ docker run -d --name matomo -p 80:80 -p 443:443 \
--net matomo_network \
-e MARIADB_HOST=mariadb \
-e MARIADB_PORT_NUMBER=3306 \
@ -369,7 +369,7 @@ To configure Matomo to send email using SMTP you can set the following environme
* `MATOMO_SMTP_PROTOCOL`: Matomo SMTP protocol to use. Available protocols are: "ssl", "tls", "none". No default.
* `MATOMO_SMTP_AUTH`: Matomo SMTP authentication mechanism to use. Available mechanisms are: "Plain", "Login", "Crammd5". Default: **Plain**.
##### SMTP Example
##### SMTP example
This would be an example of SMTP configuration using a Gmail account:
@ -392,7 +392,7 @@ This would be an example of SMTP configuration using a Gmail account:
* For manual execution:
```console
docker run -d --name matomo -p 80:8080 -p 443:8443 \
docker run -d --name matomo -p 80:8080 -p 443:8443 \
--env MATOMO_DATABASE_USER=bn_matomo \
--env MATOMO_DATABASE_NAME=bitnami_matomo \
--env MATOMO_SMTP_HOST=smtp.gmail.com \