Database docs fix #517
Merged
Database docs fix #517
Conversation
This file contains 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
…be also some database config lines
|
Hint for future. Please use |
|
I canceled the travis build as it's not required for this PR. |
| @@ -28,6 +28,9 @@ mysql -h localhost -u user -p -e 'create database mongooseim' | |||
| mysql -h localhost -u user -p mongooseim < mysql.sql | |||
| ``` | |||
|
|
|||
| You should also configure MySQL database in `[MongooseIM root]/rel/files/ejabberd.cfg` file. | |||
There was a problem hiding this comment.
I think it's enough to say "ejabberd.cfg file" instead of the path. The thing is that the ejabberd.cfg file described in Advanced-configuration.md is a template for the final config file. This, I think, should be stated in the Advanced configuration.
Same applies to next 2 changes.
ludwikbukowski
force-pushed
the
database_docs_fix
branch
from
474ced3 to
0986207
Compare
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 of database configuration in docs was in two seperated locations, so I made them reffering on each other.