I guess this should rather be a separate project or a part of https://github.com/matomo-org/docker than in the main repository.

@dshiryaev-plesk I noticed you're thumbs down. I suppose we would be wanting max a link to our official docker but for sure not want to maintain another docker. There's also the problem that we would need to potentially maintain the SQL fixture over time etc and having this in this repository doesn't quite work for us as we wouldn't even really be able to support and maintain it. Might be better to put it in a standalone repository?

@tsteur what do you reckon we do here?
@dshiryaev-plesk any thoughts?

I still think that this shouldn't be in the main repo as it means that it needs to be maintained together with Matomo itself. (and having an SQL file in Matomo means people take it as official and will complain once it doesn't work)
I'm proposing:

• adding it to https://github.com/matomo-org/docker as the use case overlaps with it and maintaining two independent projects is a lot of useless work
• or adding it as a new https://github.com/matomo-org/docker-compose (or something like that) repo and having it maintained by someone
• or keeping it a seperate project just like https://github.com/bitnami/bitnami-docker-matomo and https://github.com/crazy-max/docker-matomo

@J0WI What's your opinion?

Definitely wouldn't merge in this repo.

I think it's the best to just use FROM matomo and add whatever you need for development. We should not add xdebug to https://github.com/matomo-org/docker and definitely not on DockerHub.
A minimal docker-compose.yml example could also be added to https://github.com/docker-library/docs/tree/master/matomo, but the example here is far more complex than what is required to play with this container.

Closing this issue for now as we agreed we don't really want to have this in core. @dshiryaev-plesk maybe look at the last comments re what could be done?