WIP: Migration Guide For Moving To A New Server #18
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
|
So added my second guide too now. Is it synced automatically or would I have to tell the GitHub that there is a new commit now? (Sorry Mr. Burns, this is my first day :D) |
|
I think I'm reasonably happy with this now, would be awesome if someone could do a sanity check and try it out. (And I am not saying this because I don't want to, I am saying this so the other one is not biased by my experiences and thus better in following what I wrote here, if that makes sense?) |
|
I'll take a look at it ;) |
Signed-off-by: Maurice Preuß (envoyr) <envoyr@froxlor.org>
improvement of the introduction and proper names
…etters in their name
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 seriously hope I did it right, or right enough for it to work.
Anyway, here's my first version of a migration guide to move Froxlor to a new server. This is EZ Mode with just cloning the mysql directory.
What's missing is hard mode where we create and import the databases afresh so we get rid of any residue from the old server. Which is also more flexible because this would allow to for example switch MariaDB<>MySQL, and you don't have to have the same version and whatnot.