Add instructions on encoding database password #1606
Merged
Conversation
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
|
I'm pretty sure this will help/prevent others to spent time debugging the issue. |
|
@glye before proofing: do you think we could move the bulk of the text to https://doc.ibexa.co/en/master/getting_started/troubleshooting, and leave only a mention and link on this page? That would prevent overfilling the install guide with too many "special concerns". |
|
@DominikaK Sure, that would be fine. |
adamwojs
approved these changes
May 4, 2022
added 2 commits
May 4, 2022 11:10
DominikaK
approved these changes
May 4, 2022
DominikaK
pushed a commit
that referenced
this pull request
May 5, 2022
DominikaK
pushed a commit
that referenced
this pull request
May 5, 2022
DominikaK
pushed a commit
that referenced
this pull request
May 5, 2022
|
Thanks for the work on this guys 👏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Based on this community question: https://ezcommunity.slack.com/archives/C032PD5N9UY/p1651091978286979
we should document that database passwords has certain limitations. I'm following this recommendation: symfony/symfony#35568 (comment)
and adding the alternative of simply using chars that require no encoding.
I am not sure if using headers inside the tip box works as intended. Also not sure how much entropy discussion is worthwhile here, we want to keep it short but understandable.