Recommend MySQL for production setups #1281
Merged
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
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.
I updated
renterdto suggest MySQL for production usage, in my opinion making a distinction between small/personal nodes and anything else confuses people. It's also kind of annoying because if you turn your 10TB node into a 100TB node you'll have to migrate databases. I know SQLite works perfectly fine up until 50TB+ even but since MySQL performs better we might as well suggest it for usage in production?Extending docs with MySQL setup guides can be tracked here SiaFoundation/docs#77 - I don't think we need to add that to
renterd'sREADME.