matomo-org / matomo-org/docker

Missing internal network on apache example compose file

Open
#334 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
1k
Forks
384
PR merge metrics
No merged PRs in 30d

Description

The current docker-compose.yml inside the .example/apache folder is missing an internal network to allow the app service to connect to the db service.

This is my current working docker-compose file:

```yml
version: "3"

services:
db:
image: mariadb:10.11
command: --max-allowed-packet=64MB
restart: always
volumes:
- db:/var/lib/mysql:Z
env_file:
- ./db.env
networks:
- matomo-network

app:
container_name: matomo
image: matomo
restart: always
volumes:
# - ./config:/var/www/html/config:z
# - ./logs:/var/www/html/logs:z
- matomo:/var/www/html:z
environment:
- MATOMO_DATABASE_HOST=db
env_file:
- ./db.env
expose:
- 80
networks:
- matomo-network
- reverse-proxy-network

volumes:
db:
matomo:

networks:
matomo-network:
reverse-proxy-network:
external: true

```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open .example/apache/docker-compose.yml and compare its service network configuration with the working Compose example in the issue. Verify that the app and db services can communicate over the intended internal network, while preserving the existing reverse-proxy setup. Done means the example file contains the required network configuration for app-to-db connectivity.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose
Domain
devops
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.