Update all docker-compose files to use the same version and examples#2159
Update all docker-compose files to use the same version and examples#2159polarathene merged 7 commits intodocker-mailserver:masterfrom williamdes:docs-fix
Conversation
wernerfred
left a comment
There was a problem hiding this comment.
All in all thanks for syncing up all those examples.
But i really dislike inline comments (no benefit except for extra work when automating and scripting stuff)
So if we really need those comments at all then please put them in the line above. As most of the occurences are examples imho it is fine to keep mail and example.com . I think we can expect this level of knowledge transfer capacity of people that want to run their own mailserver.
Well, let me know what example if best so I can sync all of them |
|
I think this is fine (current README): |
georglauterbach
left a comment
There was a problem hiding this comment.
Two small changes I proposed. Other than that, LGTM 👍🏼
This comment has been minimized.
This comment has been minimized.
| - ONE_DIR=1 | ||
| - DMS_DEBUG=0 | ||
| - SPOOF_PROTECTION=0 | ||
| - REPORT_RECIPIENT=1 |
There was a problem hiding this comment.
By the way, this is deprecated, what should it be changed to ?
The docs are not clear about that
There was a problem hiding this comment.
What exactly is deprecated? ONE_DIR ?
There was a problem hiding this comment.
There was a problem hiding this comment.
There was a problem hiding this comment.
The space count seems wrong (4 instead of 2) for the ports, volumes and environment items.
There was a problem hiding this comment.
I have already addressed indent issues in my commits. This file in particular gets it's own separate PR due to it's history and issues with it in general I've resolved, that will follow after my bulk changes PR.
|
I've aligned the volumes in |
| - ONE_DIR=1 | ||
| - DMS_DEBUG=0 | ||
| - SPOOF_PROTECTION=0 | ||
| - REPORT_RECIPIENT=1 |
There was a problem hiding this comment.
polarathene
left a comment
There was a problem hiding this comment.
This looks great @williamdes ! Thanks for addressing this 😀
An observation that I couldn't easily add a review comment on, was some inconsistencies in volumes. The main concern with that being older data volumes mapping vs newer bind mount volumes that we changed to by default this year.
Any of these mappings should take precedence over the previous data volumes usage I think?:
volumes:
- ./data/maildata:/var/mail
- ./data/mailstate:/var/mail-state
- ./data/maillogs:/var/log/mail
- /etc/localtime:/etc/localtime:ro
- ./config/:/tmp/docker-mailserver/May be easiest to search based on the the internal mapped location, there is bind mount examples using ./data/ prefix followed by mail,state,logs` as a variant too. Perhaps we should make that consistent?
./data/mail* seems redundant vs ./data/* for the prefix, alternatively unify the config volume under the same hierarchy, ie: ./data/config/.
Since some compose examples have other services doing local mounts, might want to group those volumes to the context of the service (dms):
./dms/config/and./dms/data/*(mail, state, logs).- or
./data/dms/config/and./data/dms/*.
Some examples only mount some of those volumes, I assume because the others aren't required for the example.
In the ssl.md doc, nginx related services are using absolute volume paths like /mnt/data/nginx, should probably match relative path as well (except for /var/run/docker.sock). The related dms container just has ./mail and ./mail-state and mixes in the absolute nginx path to share the cert.
On basic-installation.md, I believe @wernerfred might have created this doc from splitting a wiki article of his during the migration to new docs. It needs to be reviewed from the looks of it as it includes the volume mount: /var/ds/wsproxy/letsencrypt/:/etc/letsencrypt/, this is described further down on the page, but the referenced docker image isn't included in the compose example above, I don't think the absolute path is required? If updating this keep in mind the content on the document outside the config snippet referencing it.
As the example docker-compose.yml at the root of the git repo has comments to provide guidance on ports, should there also be one above hostname to clarify that the two properties define the FQDN mail.example.com? I think when I first encountered that (not something I was used to configuring before docker-mailserver), I was initially confused with what to expect.
| containers: | ||
| - name: mailserver | ||
| image: ghcr.io/docker-mailserver/docker-mailserver:10.0.0 | ||
| image: ghcr.io/docker-mailserver/docker-mailserver:latest |
There was a problem hiding this comment.
| image: ghcr.io/docker-mailserver/docker-mailserver:latest | |
| image: docker.io/docker-mailserver/docker-mailserver:latest |
There was a problem hiding this comment.
Why not change this to docker.io? (this was marked as resolved)
There was a problem hiding this comment.
I have done so on my additions. I marked this as resolved when I committed it.
Originally I was going to push here, but other changes piled up. If you would like I can commit the suggestion here and rebase my changes on top?
|
Hi, |
No immediate rush for this AFAIK. Thanks for letting us know, if someone has the time to spare we'll leave a comment upon picking it up :) |
|
I am now wrapping up this PR. |
|
My additions are too large to mix into this PR. I have some questions aimed at my changes and due to the noise it would add, I think it's better addressed via separate PR than to dirty the review state that reached approval here. Unfortunately it seems there's some conflicts already, I'll address those and we can approve/merge? |
1b1c07a
|
Documentation preview for this PR is ready! 🎉 Built with commit: 1b1c07a |
polarathene
left a comment
There was a problem hiding this comment.
Resolved the conflicts. setup.sh.md and mailserver-behind-proxy.md updated to main branch.
Description
Update all docker-compose files to use the same version and examples
Type of change
Checklist:
docs/)