This repository has been archived by the owner on Sep 29, 2023. It is now read-only.
Add migration docs #399
Merged
Add migration docs #399
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
gewenyu99
commented
Jul 20, 2023
app/views/docs/migration.phtml
Outdated
|
|
||
| <h2><a href="#limitations" id="limitations">Limitations</a></h2> | ||
| <p> | ||
| [TODO] @bradley help me out here. include performance, feature, all things annoying |
There was a problem hiding this comment.
@PineappleIOnic here
gewenyu99
commented
Jul 20, 2023
| @@ -0,0 +1,3 @@ | |||
| <p> | |||
| [TODO: Bradley try to fill this in with necessary information + limitations] | |||
There was a problem hiding this comment.
This document should contain everything a user needs to know about migrating from Firebase to Appwrite, don't worry about looking pretty, get the information down first, we'll edit this and use flow as template for other providers
Start work Docs
|
|
|
Meldiron
reviewed
Aug 25, 2023
Meldiron
reviewed
Aug 25, 2023
Meldiron
reviewed
Aug 25, 2023
| <li>Appwrite will not incur usage charges during migrations, but Firebase may still incur service charges.</li> | ||
| <li>Appwrite Migrations only supports Firestore as a database source. Realtime Database is <b>currently not supported</b>.</li> | ||
| <li>At the moment only top level document migration is supported. Nested documents will not be transferred automatically.</li> | ||
| <li>OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.</li> |
There was a problem hiding this comment.
Let's also mention that Functions will not be transferred, and that developer needs to rewrite functions to use Appwrite syntax
Meldiron
reviewed
Aug 25, 2023
Meldiron
reviewed
Aug 25, 2023
| Click on the <b>Create Migration</b> button and select <b>Firebase</b> as your source. | ||
| </li> | ||
| <li> | ||
| Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. |
There was a problem hiding this comment.
I think it's always manual way. @PineappleIOnic can confirm
There was a problem hiding this comment.
I thought we had an service account.
Meldiron
reviewed
Aug 25, 2023
Meldiron
reviewed
Aug 25, 2023
| discover your Firebase projects. Simply select the source project and follow the migration wizard. | ||
| </p> | ||
|
|
||
| <p>After completing the migration wizard, migration will begin. Return to step 4 of <a href="#migration-process">the migration steps</a>.</p> |
There was a problem hiding this comment.
I cant see any step 4 in this file
There was a problem hiding this comment.
You'll see it when it's rendered
Meldiron
reviewed
Aug 25, 2023
| Upload the JSON file to Appwrite and follow the migration wizard. | ||
| </li> | ||
| <li> | ||
| After completing the migration wizard, migration will begin. Return to step 4 of <a href="#migration-process">the migration steps</a>. |
There was a problem hiding this comment.
I cant see step 4 in this file
There was a problem hiding this comment.
You'll see it when it's rendered
Meldiron
approved these changes
Aug 25, 2023
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Co-authored-by: Matej Bačo <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)