docs: Debugging - Correctly starting DMS#3654
Merged
georglauterbach merged 1 commit intomasterfrom Nov 25, 2023
Merged
Conversation
Contributor
|
Documentation preview for this PR is ready! 🎉 Built with commit: 1c3d507 |
georglauterbach
approved these changes
Nov 25, 2023
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Previously suggested in Aug 2023: #3482
@georglauterbach is managing the v13 release, so I've set the milestone to v13.1 in case this misses the v13 release window.
Presently there is a fairly clear and early mention of this advice in the docs:
docker-mailserver/docs/content/usage.md
Lines 120 to 126 in 2a716cf
This PR just adds a more verbose variant to explain the problem better and place it in a location users are more likely to land at when troubleshooting (because who reads docs in full these days? 😆 ).
Preview
Reference
List of
--force-recreatebeing used / suggested to troubleshoot (not filtered to when it was the solution):