-
-
Notifications
You must be signed in to change notification settings - Fork 2k
docs: Remove ENV ONE_DIR
#3840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Remove ENV ONE_DIR
#3840
Conversation
34f222d to
c146b76
Compare
c146b76 to
d14db98
Compare
Only `ONE_DIR=0` has any effect. As the actual feature is now dependent upon the `/var/mail-state` location existing. It is advised not mounting anything there instead if wanting to avoid runtime state consolidation.
This is more search friendly / organized to find references to all DMS volumes.
d14db98 to
3eba74d
Compare
|
Just some thoughts on the lint failure as I didn't expect this (feel free to ignore this comment):
# 0 for missing final newline, 1 for present:
$ tail -c 1 docs/content/config/environment.md | wc -l
0We already have that prevented by a recent PR for user config parsing (where the last report was related to VSCode defaults), and the ECLint check config catches it here in PRs. Perhaps a git pre-commit hook could better prevent it (I haven't checked if that's implicit, or requires the contributor to use an editor plugin like for I'm wondering if there's any value in highlighting that default setting for VSCode in our docs (with required configuration change) 🤔 VSCode otherwise expects a blank line (a separate setting enabled by default optionally also renders it as a separate blank line visually): |
VSCode by default excludes this if the last line rendered is removed (rendered as a separate blank line). A separate setting can enforce adding the final newline upon save regardless.
|
I have "files.trimTrailingWhitespace": trueis useful as well. |
georglauterbach
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the first commit in particular; it always bothered me how we only document the volumes in the FAQ 👍🏼
|
I'll leave this a little bit longer for @casperklein to possibly chime in since I recall |
|
Short and sweet:
I am also using this in VSCode: |
I can't think of any issues this PR introduces in this regard; it would be a problem if someone mounted a volume to the paths we specify in our docs but then sets |
|
Documentation preview for this PR is ready! 🎉 Built with commit: 41359fe |
PR - docker-mailserver/docker-mailserver#3840 Signed-off-by: Aldo Maria Vizcaino <[email protected]>
PR - docker-mailserver/docker-mailserver#3840 Signed-off-by: Aldo Maria Vizcaino <[email protected]>



Description
I don't see this as a breaking change given the logic we have for it.
ONE_DIR./var/mail-statelocation existing is the real detection for triggering the runtime-state consolidation feature.ONE_DIRchanges in docs relates to centralizing the docs for our DMS state volume).I've explained DMS Volumes several times in past issues (example), so that should be a helpful addition to reference to link users to instead 👍
Type of change
Checklist:
docs/)CHANGELOG.md