From 9ea4f2c75c3859e8cefd7f296f14bc0cfdaf4eb0 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 20 Jul 2023 20:38:36 +0000 Subject: [PATCH 01/45] Add migrations: --- app/views/docs/index.phtml | 6 +++ app/views/docs/migration-firebase.phtml | 3 ++ app/views/docs/migration-nhost.phtml | 0 app/views/docs/migration-supabase.phtml | 0 app/views/docs/migration.phtml | 60 +++++++++++++++++++++++++ 5 files changed, 69 insertions(+) create mode 100644 app/views/docs/migration-firebase.phtml create mode 100644 app/views/docs/migration-nhost.phtml create mode 100644 app/views/docs/migration-supabase.phtml create mode 100644 app/views/docs/migration.phtml diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index 3554cba88..11c8f4882 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -93,6 +93,12 @@ $cols = [
  • Functions
    • +
  • + Migration + +
    • diff --git a/app/views/docs/migration-firebase.phtml b/app/views/docs/migration-firebase.phtml new file mode 100644 index 000000000..4f811a0ea --- /dev/null +++ b/app/views/docs/migration-firebase.phtml @@ -0,0 +1,3 @@ +

    + [TODO: Bradley try to fill this in with necessary information + limitations] +

    \ No newline at end of file diff --git a/app/views/docs/migration-nhost.phtml b/app/views/docs/migration-nhost.phtml new file mode 100644 index 000000000..e69de29bb diff --git a/app/views/docs/migration-supabase.phtml b/app/views/docs/migration-supabase.phtml new file mode 100644 index 000000000..e69de29bb diff --git a/app/views/docs/migration.phtml b/app/views/docs/migration.phtml new file mode 100644 index 000000000..9757c6526 --- /dev/null +++ b/app/views/docs/migration.phtml @@ -0,0 +1,60 @@ +

    + Moving your app from another platform to Appwrite? + You can move your app from Firebase, Supabase, NHost, and even other Appwrite projects to another Appwrite project using Migrations. + Migrations will automatically move accounts, database documents, and storage files from one source to another. +

    + +

    Supported sources

    +

    + You can transfer from these sources to an Appwrite project. +

    + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Source
    + [IMAGE] + + Firebase + +

    Migrate from Firebase

    +
    + [IMAGE] + + Supabase + +

    Migrate from Supabase

    +
    + [IMAGE] + + NHost + +

    Migrate from NHost

    +
    + +

    Limitations

    +

    + [TODO] @bradley help me out here. include performance, feature, all things annoying +

    \ No newline at end of file From 1092b844621658a60b45506e86b6af9a985e7040 Mon Sep 17 00:00:00 2001 From: Bradley Schofield Date: Mon, 31 Jul 2023 14:04:21 +0100 Subject: [PATCH 02/45] Start work on Firebase docs --- app/views/docs/migration-firebase.phtml | 58 ++++++++++++++++++++++++- app/views/docs/migration.phtml | 2 +- 2 files changed, 58 insertions(+), 2 deletions(-) diff --git a/app/views/docs/migration-firebase.phtml b/app/views/docs/migration-firebase.phtml index 4f811a0ea..835c6553e 100644 --- a/app/views/docs/migration-firebase.phtml +++ b/app/views/docs/migration-firebase.phtml @@ -1,3 +1,59 @@ +

    Things to keep in mind

    - [TODO: Bradley try to fill this in with necessary information + limitations] + - Appwrite will waive usage fees during the migration process, however Firebase may still charge you for usage on their platform. + + - At the moment only top level document migrations are supported. Nested documents will not be transferred at this moment. + + - Appwrite migrations only supports Firestore. Realtime Database is not supported at this time. + + - OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete. +

    + +

    Supported Resources

    + + + + + + + + + + + + + + + + + + + + + +
    UsersDatabasesDocumentsFilesFunctions
    Firebase✅✅✅✅
    + +

    Migrating to Appwrite from Firebase

    +

    + To begin migrating to Appwrite make sure to read the migration overview and + things to keep in mind sections above. + + To begin you can either migrate while creating a new project or go into your project settings and click on the "Migrations" tab. + + Next click on the "Create Migration" button and select "Firebase" as your source. + +

    Migrating to Appwrite Cloud

    + To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically + discover your Firebase projects then you can simply just select the project you want to migrate from. + +

    Migrating to Appwrite Self-Hosted

    + If you are self-hosting Appwrite you will need to create a service account in your Firebase project and download the JSON file. + + To create a service account navigate to your Firebase console then click on the gear icon and select "Project Settings". + Next click on the "Service Accounts" tab and click on the "Generate New Private Key" button to download the JSON file. + + + + Once you have the JSON file downloaded you can click on "Manual Authentication" while going through the migration process and\ + upload the JSON file.

    \ No newline at end of file diff --git a/app/views/docs/migration.phtml b/app/views/docs/migration.phtml index 9757c6526..542744618 100644 --- a/app/views/docs/migration.phtml +++ b/app/views/docs/migration.phtml @@ -56,5 +56,5 @@

    Limitations

    - [TODO] @bradley help me out here. include performance, feature, all things annoying + - Migrations cannot transfer all data perfectly, so certain fields, such as $createdAt and $updatedAt, may not be transferred. More information can be found on the migration page for each source.

    \ No newline at end of file From 7e10cc90feee9dc24849aab3e87f493f7b89d755 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Mon, 31 Jul 2023 19:44:12 +0000 Subject: [PATCH 03/45] Did some formatting --- app/views/docs/migration-firebase.phtml | 79 +++++++++++++++++-------- 1 file changed, 54 insertions(+), 25 deletions(-) diff --git a/app/views/docs/migration-firebase.phtml b/app/views/docs/migration-firebase.phtml index 835c6553e..300fbfd43 100644 --- a/app/views/docs/migration-firebase.phtml +++ b/app/views/docs/migration-firebase.phtml @@ -1,15 +1,20 @@ -

    Things to keep in mind

    - - Appwrite will waive usage fees during the migration process, however Firebase may still charge you for usage on their platform. - - - At the moment only top level document migrations are supported. Nested documents will not be transferred at this moment. + Moving your project from Firebase to Appwrite? + Appwrite Migrations can help you streamline the process. + + Here's what you need to know to get started. +

    - - Appwrite migrations only supports Firestore. Realtime Database is not supported at this time. +

    Things to keep in mind

    - - OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete. -

    +
      +
    1. Appwrite will not charge usage during migrations, but Firebase may still incur service charges.
      2. +
    2. Appwrite migrations only supports Firestore as a database source. Realtime Database is currently not supported.
      3. +
    3. At the moment only top level document migration is supported. Nested documents will not be transferred automatically.
      4. +
    4. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
      5. +
    -

    Supported Resources

    +

    Supported resource types

    @@ -35,25 +40,49 @@

    Migrating to Appwrite from Firebase

    - To begin migrating to Appwrite make sure to read the migration overview and - things to keep in mind sections above. - - To begin you can either migrate while creating a new project or go into your project settings and click on the "Migrations" tab. - - Next click on the "Create Migration" button and select "Firebase" as your source. + To begin migrating to Appwrite make sure to read the migration overview + and things to keep in mind sections above. +

    + +
      +
    1. + Create a new project and click on the Migrations tab. +
      2. +
    2. + Click on the Create Migration button and select Firebase as your source. +
      3. +
    3. + Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. +
      4. +
    -

    Migrating to Appwrite Cloud

    - To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically - discover your Firebase projects then you can simply just select the project you want to migrate from. -

    Migrating to Appwrite Self-Hosted

    - If you are self-hosting Appwrite you will need to create a service account in your Firebase project and download the JSON file. - To create a service account navigate to your Firebase console then click on the gear icon and select "Project Settings". - Next click on the "Service Accounts" tab and click on the "Generate New Private Key" button to download the JSON file. +

    Appwrite Cloud

    +

    + To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically + discover your Firebase projects. Simply select the source project and follow the migration wizard. +

    - +

    Migrating to Appwrite Self-Hosted

    +

    + If you are self-hosting Appwrite you will need to create a service account in your Firebase project and download the JSON file. +

    - Once you have the JSON file downloaded you can click on "Manual Authentication" while going through the migration process and\ - upload the JSON file. -

    \ No newline at end of file +
      +
    1. + Navigate to your Firebase console. +
      2. +
    2. + Click the gear icon to access your Project Settings. +
      3. +
    3. + Click Service Accounts, then Generate New Private Key. Don't share this key with anyone! +
      4. +
    4. + Once you've downloaded your private key, head back to Appwrite and click Manual Authentication. +
      5. +
    5. + Upload the JSON private key and follow the wizard. +
      6. +
    From a76e1ea5536ce4908fd5e2e8f2d7319a376c0e15 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Wed, 2 Aug 2023 19:09:58 +0000 Subject: [PATCH 04/45] Added instructions for setup to include adding platforms --- app/views/docs/migration-firebase.phtml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/app/views/docs/migration-firebase.phtml b/app/views/docs/migration-firebase.phtml index 300fbfd43..2d4951cc2 100644 --- a/app/views/docs/migration-firebase.phtml +++ b/app/views/docs/migration-firebase.phtml @@ -52,12 +52,14 @@ Click on the Create Migration button and select Firebase as your source.
  • - Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. + Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. + See the Cloud and Self-hosting sections for details. +
    • +
  • + Finally, add the platforms for your Web, Flutter, Android, and iOS apps.
    • - -

    Appwrite Cloud

    To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically From b4fb7387e93fe53a59f37da3322eac3e5c03a60b Mon Sep 17 00:00:00 2001 From: Bradley Schofield Date: Thu, 3 Aug 2023 00:50:36 +0100 Subject: [PATCH 05/45] Add docs for cloud to local and visa-versa --- app/views/docs/cloud-to-local.phtml | 33 ++++++++++++++++++++++++++++ app/views/docs/local-to-cloud.phtml | 34 +++++++++++++++++++++++++++++ 2 files changed, 67 insertions(+) create mode 100644 app/views/docs/cloud-to-local.phtml create mode 100644 app/views/docs/local-to-cloud.phtml diff --git a/app/views/docs/cloud-to-local.phtml b/app/views/docs/cloud-to-local.phtml new file mode 100644 index 000000000..160c35c07 --- /dev/null +++ b/app/views/docs/cloud-to-local.phtml @@ -0,0 +1,33 @@ +

    + Want to leave the cloud and move your stuff to a Self Hosted instance? We're sorry to see you go, but we've got your back. + Migrations makes it easy as easy as a couple clicks to move all of your cloud data to a Self Hosted instance. +

    + +

    Things to keep in mind

    + +
      +
    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. +
    2. Your Appwrite Instace must be accessible from the internet for the migration to work.
      3. +
    + +

    Migrating to Self Hosted from Cloud

    + +

    + To begin migrating to Appwrite Self Hosted make sure to read the migration overview + and things to keep in mind sections above. +

    + +

    + Navigate to your Appwrite Cloud and click on the Migrations tab. + + From there you can click on the Export to Self Hosted button, you will then be asked to input the URL of your Self Hosted instance + aswell as an optional feedback question asking why Self Hosted is a better fit for you. Once done you can click on the Continue button and you will be + redirected to your Self Hosted instance to continue the migration process. + + Once your at Self Hosted instance you will be prompted to select the organization aswell as the option to either create a new project + or select an existing project to migrate to. + + After you have selected the project you want to migrate to you will be asked what data you want to migrate. You can select + to migrate users, databases, documents, files and functions. Once you have selected what data you want to migrate you can + click on the Start Migration button to begin the migration process. +

    diff --git a/app/views/docs/local-to-cloud.phtml b/app/views/docs/local-to-cloud.phtml new file mode 100644 index 000000000..3648b25ee --- /dev/null +++ b/app/views/docs/local-to-cloud.phtml @@ -0,0 +1,34 @@ +

    + Making the move to Appwrite Cloud? We've got your back. + Migrations makes it easy as easy as a couple clicks to move all of your self hosted data to Appwrite Cloud. +

    + +

    Things to keep in mind

    + +
      +
    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. +
    + +

    Migrating to Cloud from Self Hosted

    +

    + To begin migrating to Appwrite Self Hosted make sure to read the migration overview + and things to keep in mind sections above. +

    + +

    + Navigate to your Self Hosted instance and click on the Migrations tab. + + From there you can click on the Deploy to Cloud button, you will then be redirected to Appwrite Cloud. + + Once your at Appwrite Cloud you will be prompted to select the organization aswell as the option to either create a new project + or select an existing project to migrate to. + + After you have selected the project you want to migrate to you will be asked what data you want to migrate. You can select + to migrate users, databases, documents, files and functions. Once you have selected what data you want to migrate you can + click on the Start Migration button to begin the migration process. +

    + +
    +

    Keep in mind

    +

    Your Self Hosted instance will generate a API Key in the background to pass to Cloud. You can revoke this key after the migration process is complete.

    +
    \ No newline at end of file From 573755c693697d5bc26cdd76cb4cc245e7b32628 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 3 Aug 2023 21:58:08 +0000 Subject: [PATCH 06/45] Fix cloud -> local --- app/views/docs/cloud-to-local.phtml | 33 ------------------- app/views/docs/migration-cloud-to-local.phtml | 33 +++++++++++++++++++ ...d.phtml => migration-local-to-cloud.phtml} | 0 3 files changed, 33 insertions(+), 33 deletions(-) delete mode 100644 app/views/docs/cloud-to-local.phtml create mode 100644 app/views/docs/migration-cloud-to-local.phtml rename app/views/docs/{local-to-cloud.phtml => migration-local-to-cloud.phtml} (100%) diff --git a/app/views/docs/cloud-to-local.phtml b/app/views/docs/cloud-to-local.phtml deleted file mode 100644 index 160c35c07..000000000 --- a/app/views/docs/cloud-to-local.phtml +++ /dev/null @@ -1,33 +0,0 @@ -

    - Want to leave the cloud and move your stuff to a Self Hosted instance? We're sorry to see you go, but we've got your back. - Migrations makes it easy as easy as a couple clicks to move all of your cloud data to a Self Hosted instance. -

    - -

    Things to keep in mind

    - -
      -
    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. -
    2. Your Appwrite Instace must be accessible from the internet for the migration to work.
      3. -
    - -

    Migrating to Self Hosted from Cloud

    - -

    - To begin migrating to Appwrite Self Hosted make sure to read the migration overview - and things to keep in mind sections above. -

    - -

    - Navigate to your Appwrite Cloud and click on the Migrations tab. - - From there you can click on the Export to Self Hosted button, you will then be asked to input the URL of your Self Hosted instance - aswell as an optional feedback question asking why Self Hosted is a better fit for you. Once done you can click on the Continue button and you will be - redirected to your Self Hosted instance to continue the migration process. - - Once your at Self Hosted instance you will be prompted to select the organization aswell as the option to either create a new project - or select an existing project to migrate to. - - After you have selected the project you want to migrate to you will be asked what data you want to migrate. You can select - to migrate users, databases, documents, files and functions. Once you have selected what data you want to migrate you can - click on the Start Migration button to begin the migration process. -

    diff --git a/app/views/docs/migration-cloud-to-local.phtml b/app/views/docs/migration-cloud-to-local.phtml new file mode 100644 index 000000000..5927d792c --- /dev/null +++ b/app/views/docs/migration-cloud-to-local.phtml @@ -0,0 +1,33 @@ +

    + Moving to a self-hosted instance? We've got you covered. + Migrations makes it easy as easy as a couple clicks to move all of your Appwrite Cloud project data to a self-hosted instance. +

    + +

    Things to keep in mind

    + +
      +
    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. +
    2. Your Appwrite Instace must be accessible from the internet for the migration to work.
      3. +
    + +

    Migrating to Self-hosted from Cloud

    + +

    + To begin migrating to Appwrite Self Hosted make sure to read the migration overview + and things to keep in mind sections above. +

    + +

    Steps on Your Cloud Project

    +
      +
    1. Navigate to your Appwrite Cloud Console and click on the Migrations tab.
      2. +
    2. Click Export to Self Hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
      3. +
    3. Optionally, tell us about why you're moving to self-hosted.
      4. +
    4. After clicking Continue, you'll be directed back to your self-hosted project to complete the process.
      5. +
    + +

    Steps on Your Self-hosted Project

    +
      +
    1. Once redirected to your self-hosted project, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
      2. +
    2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
      3. +
    3. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
      4. +
    \ No newline at end of file diff --git a/app/views/docs/local-to-cloud.phtml b/app/views/docs/migration-local-to-cloud.phtml similarity index 100% rename from app/views/docs/local-to-cloud.phtml rename to app/views/docs/migration-local-to-cloud.phtml From b84453104cbacea6743e38fee8e0068d328a645d Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 4 Aug 2023 14:59:52 +0000 Subject: [PATCH 07/45] Complete appwrite->appwrite guides --- app/views/docs/migration-cloud-to-local.phtml | 9 +++--- app/views/docs/migration-local-to-cloud.phtml | 32 +++++++++++-------- 2 files changed, 23 insertions(+), 18 deletions(-) diff --git a/app/views/docs/migration-cloud-to-local.phtml b/app/views/docs/migration-cloud-to-local.phtml index 5927d792c..3f601a2ec 100644 --- a/app/views/docs/migration-cloud-to-local.phtml +++ b/app/views/docs/migration-cloud-to-local.phtml @@ -1,26 +1,27 @@

    Moving to a self-hosted instance? We've got you covered. - Migrations makes it easy as easy as a couple clicks to move all of your Appwrite Cloud project data to a self-hosted instance. + Migrations makes it as easy as a couple clicks to move all of your Appwrite Cloud project data to a self-hosted instance.

    Things to keep in mind

    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. -
    2. Your Appwrite Instace must be accessible from the internet for the migration to work.
      3. +
    3. Your self-hosted Appwrite project must be accessible from the internet for the migration to work.
      4. +
    4. Migrations are non-destructive. No data will be deleted or lost in the source project.

    Migrating to Self-hosted from Cloud

    - To begin migrating to Appwrite Self Hosted make sure to read the migration overview + To begin migrating to Appwrite Self-hosted, make sure to read the migration overview and things to keep in mind sections above.

    Steps on Your Cloud Project

    1. Navigate to your Appwrite Cloud Console and click on the Migrations tab.
      2. -
    2. Click Export to Self Hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
      3. +
    3. Click Export to Self-hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
    4. Optionally, tell us about why you're moving to self-hosted.
    5. After clicking Continue, you'll be directed back to your self-hosted project to complete the process.
    diff --git a/app/views/docs/migration-local-to-cloud.phtml b/app/views/docs/migration-local-to-cloud.phtml index 3648b25ee..e30783d4b 100644 --- a/app/views/docs/migration-local-to-cloud.phtml +++ b/app/views/docs/migration-local-to-cloud.phtml @@ -1,34 +1,38 @@

    Making the move to Appwrite Cloud? We've got your back. - Migrations makes it easy as easy as a couple clicks to move all of your self hosted data to Appwrite Cloud. + Migrations makes it as easy as a couple clicks to move all of your self-hosted project data to a Cloud instance.

    Things to keep in mind

    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. +
    2. Your self-hosted Appwrite project must be accessible from the internet for the migration to work.
      3. +
    3. Migrations are non-destructive. No data will be deleted or lost in the source project.
    -

    Migrating to Cloud from Self Hosted

    +

    Migrating to Self-hosted from Cloud

    - To begin migrating to Appwrite Self Hosted make sure to read the migration overview + To begin migrating to self-hosted, make sure to read the migration overview and things to keep in mind sections above.

    -

    - Navigate to your Self Hosted instance and click on the Migrations tab. - - From there you can click on the Deploy to Cloud button, you will then be redirected to Appwrite Cloud. +

    Steps on Your Self-hosted Project

    - Once your at Appwrite Cloud you will be prompted to select the organization aswell as the option to either create a new project - or select an existing project to migrate to. +
      +
    1. Navigate to your self-hosted project's console and click on the Migrations tab.
      2. +
    2. Click Deploy to cloud, you will be redirected to Appwrite Cloud.
      3. +
    3. You will complete the migration on Appwrite Cloud.
      4. +
    - After you have selected the project you want to migrate to you will be asked what data you want to migrate. You can select - to migrate users, databases, documents, files and functions. Once you have selected what data you want to migrate you can - click on the Start Migration button to begin the migration process. -

    +

    Steps on Your Cloud Project

    +
      +
    1. Once redirected to Appwrite Cloud, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
      2. +
    2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
      3. +
    3. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
      4. +

    Keep in mind

    -

    Your Self Hosted instance will generate a API Key in the background to pass to Cloud. You can revoke this key after the migration process is complete.

    +

    Your Self-hosted instance will generate a API Key in the background to pass to Cloud. You can revoke this key after the migration process is complete.

    \ No newline at end of file From 46ffc50db33703f4a9191e4ae226fca2a5aa27b5 Mon Sep 17 00:00:00 2001 From: Bradley Schofield Date: Tue, 15 Aug 2023 10:23:07 +0100 Subject: [PATCH 08/45] Add NHost and Supabase Docs --- app/views/docs/migration-nhost.phtml | 88 ++++++++++++++++++++++++ app/views/docs/migration-supabase.phtml | 91 +++++++++++++++++++++++++ 2 files changed, 179 insertions(+) diff --git a/app/views/docs/migration-nhost.phtml b/app/views/docs/migration-nhost.phtml index e69de29bb..154555757 100644 --- a/app/views/docs/migration-nhost.phtml +++ b/app/views/docs/migration-nhost.phtml @@ -0,0 +1,88 @@ +

    + Moving your project from NHost to Appwrite? + Appwrite Migrations can help you streamline the process. + + Here's what you need to know to get started. +

    + +

    Things to keep in mind

    + +
      +
    1. Appwrite will not charge usage during migrations, but NHost may still incur service charges.
      2. +
    2. Appwrite's Database doesn't support all the features of the postgreSQL database so more advanced postgres centric things things like advanced indexes, postgres functions and scheduling will not be migrated.
      3. +
    3. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
      4. +
    + +

    Supported resource types

    +
    + + + + + + + + + + + + + + + + + + + + +
    UsersDatabasesDocumentsFilesFunctions
    NHost✅✅✅✅
    + +

    Migrating to Appwrite from NHost

    +

    + To begin migrating to Appwrite make sure to read the migration overview + and things to keep in mind sections above. +

    + +
      +
    1. + Create a new project and click on the Migrations tab. +
      2. +
    2. + Click on the Create Migration button and select NHost as your source. +
      3. +
    3. + Enter the credentials following the instructions below and click Next. +
      4. +
    4. + Select the resources you want to migrate and finally click Start migration to begin the migration process. +
      5. +
    + +

    Migrating to Appwrite from NHost

    +

    +

      +
    1. + Enter all the following credentials from your NHost project. +
        +
      • + Region - The region your NHost project is hosted in. This can be found in your NHost project environment variables as NHOST_REGION. +
        • +
      • + Subdomain - The subdomain of your NHost project. This can be found in your NHost project environment variables as NHOST_SUBDOMAIN. +
        • +
      • + Database - The name of your NHost database. This can be found in your NHost project Database settings. +
        • +
      • + Username - The username of your NHost database. This can be found in your NHost project Database settings. +
        • +
      • + Password - The password of your NHost database. You set this when you created your NHost project, if you don't remember it you can reset it from your NHost project Database settings. +
        • +
      • + Admin Secret - The admin secret of your NHost project. This can be found in your NHost project environment variables as NHOST_ADMIN_SECRET. We use this to transfer your NHost Files to Appwrite. +
        • +
      +
      2. +
    +

    \ No newline at end of file diff --git a/app/views/docs/migration-supabase.phtml b/app/views/docs/migration-supabase.phtml index e69de29bb..76f0188c6 100644 --- a/app/views/docs/migration-supabase.phtml +++ b/app/views/docs/migration-supabase.phtml @@ -0,0 +1,91 @@ +

    + Moving your project from Supabase to Appwrite? + Appwrite Migrations can help you streamline the process. + + Here's what you need to know to get started. +

    + +

    Things to keep in mind

    + +
      +
    1. Appwrite will not charge usage during migrations, but Supabase may still incur service charges.
      2. +
    2. Appwrite's Database doesn't support all the features of the postgreSQL database so more advanced postgres centric things things like advanced indexes, postgres functions and scheduling will not be migrated.
      3. +
    3. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
      4. +
    + +

    Supported resource types

    + + + + + + + + + + + + + + + + + + + + + +
    UsersDatabasesDocumentsFilesFunctions
    Supabase✅✅✅✅
    + +

    Migrating to Appwrite from Supabase

    +

    + To begin migrating to Appwrite make sure to read the migration overview + and things to keep in mind sections above. +

    + +
      +
    1. + Create a new project and click on the Migrations tab. +
      2. +
    2. + Click on the Create Migration button and select Supabase as your source. +
      3. +
    3. + Enter the credentials following the instructions below and click Next. +
      4. +
    4. + Select the resources you want to migrate and finally click Start migration to begin the migration process. +
      5. +
    + +

    Migrating to Appwrite from Supabase

    +

    +

      +
    1. + Enter all the following credentials from your Supabase project. +
        +
      • + Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. +
        • +
      • + Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host. +
        • +
      • + Port - The port of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Port. By default this is 5432. +
        • +
      • + Username - The username of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Username. +
        • +
      • + Password - The password of your Supabase Database, this was set when you created your Supabase project. If you forgot it you can reset it within your Database Settings +
        • +
      • + Endpoint - This is the endpoint of your Supabase instance under Project Settings -> API. This is used to migrate your files. +
        • +
      • + API Key - This is the key of your Supabase instance under Project Settings -> API. This is used to migrate your files. Make sure to use the hidden service_role key. +
        • +
      +
      2. +
    +

    \ No newline at end of file From 7d7c029dbfc9c1e32743271a70677aeaca73d050 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 14:34:23 +0000 Subject: [PATCH 09/45] update index to have all pages --- app/views/docs/index.phtml | 14 +++++++++++++- app/views/docs/migration.phtml | 3 ++- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index 11c8f4882..dac01f024 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -96,7 +96,19 @@ $cols = [
  • Migration + + + +
    • diff --git a/app/views/docs/migration.phtml b/app/views/docs/migration.phtml index 542744618..336689026 100644 --- a/app/views/docs/migration.phtml +++ b/app/views/docs/migration.phtml @@ -56,5 +56,6 @@

    Limitations

    - - Migrations cannot transfer all data perfectly, so certain fields, such as $createdAt and $updatedAt, may not be transferred. More information can be found on the migration page for each source. + Migrations cannot transfer all data perfectly, so certain fields, such as $createdAt and $updatedAt, may not be transferred. + More information can be found on the migration page for each source.

    \ No newline at end of file From fc5ba4004d64e87dcd6f7abb9ac0593942890692 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 15:11:06 +0000 Subject: [PATCH 10/45] Fix ordered list tags and headings --- app/views/docs/migration-nhost.phtml | 54 +++++++++++----------- app/views/docs/migration-supabase.phtml | 61 ++++++++++++------------- 2 files changed, 56 insertions(+), 59 deletions(-) diff --git a/app/views/docs/migration-nhost.phtml b/app/views/docs/migration-nhost.phtml index 154555757..a556de4a0 100644 --- a/app/views/docs/migration-nhost.phtml +++ b/app/views/docs/migration-nhost.phtml @@ -58,31 +58,29 @@ -

    Migrating to Appwrite from NHost

    -

    -

      -
    1. - Enter all the following credentials from your NHost project. -
        -
      • - Region - The region your NHost project is hosted in. This can be found in your NHost project environment variables as NHOST_REGION. -
        • -
      • - Subdomain - The subdomain of your NHost project. This can be found in your NHost project environment variables as NHOST_SUBDOMAIN. -
        • -
      • - Database - The name of your NHost database. This can be found in your NHost project Database settings. -
        • -
      • - Username - The username of your NHost database. This can be found in your NHost project Database settings. -
        • -
      • - Password - The password of your NHost database. You set this when you created your NHost project, if you don't remember it you can reset it from your NHost project Database settings. -
        • -
      • - Admin Secret - The admin secret of your NHost project. This can be found in your NHost project environment variables as NHOST_ADMIN_SECRET. We use this to transfer your NHost Files to Appwrite. -
        • -
      -
      2. -
    -

    \ No newline at end of file +

    NHost Credentials

    +
      +
    1. + Enter all the following credentials from your NHost project. +
        +
      • + Region - The region your NHost project is hosted in. This can be found in your NHost project environment variables as NHOST_REGION. +
        • +
      • + Subdomain - The subdomain of your NHost project. This can be found in your NHost project environment variables as NHOST_SUBDOMAIN. +
        • +
      • + Database - The name of your NHost database. This can be found in your NHost project Database settings. +
        • +
      • + Username - The username of your NHost database. This can be found in your NHost project Database settings. +
        • +
      • + Password - The password of your NHost database. You set this when you created your NHost project, if you don't remember it you can reset it from your NHost project Database settings. +
        • +
      • + Admin Secret - The admin secret of your NHost project. This can be found in your NHost project environment variables as NHOST_ADMIN_SECRET. We use this to transfer your NHost Files to Appwrite. +
        • +
      +
      2. +
    \ No newline at end of file diff --git a/app/views/docs/migration-supabase.phtml b/app/views/docs/migration-supabase.phtml index 76f0188c6..871ca85a9 100644 --- a/app/views/docs/migration-supabase.phtml +++ b/app/views/docs/migration-supabase.phtml @@ -58,34 +58,33 @@ -

    Migrating to Appwrite from Supabase

    -

    -

      -
    1. - Enter all the following credentials from your Supabase project. -
        -
      • - Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. -
        • -
      • - Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host. -
        • -
      • - Port - The port of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Port. By default this is 5432. -
        • -
      • - Username - The username of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Username. -
        • -
      • - Password - The password of your Supabase Database, this was set when you created your Supabase project. If you forgot it you can reset it within your Database Settings -
        • -
      • - Endpoint - This is the endpoint of your Supabase instance under Project Settings -> API. This is used to migrate your files. -
        • -
      • - API Key - This is the key of your Supabase instance under Project Settings -> API. This is used to migrate your files. Make sure to use the hidden service_role key. -
        • -
      -
      2. -
    -

    \ No newline at end of file +

    Credentials

    + +
      +
    1. + Enter all the following credentials from your Supabase project. +
        +
      • + Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. +
        • +
      • + Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host. +
        • +
      • + Port - The port of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Port. By default this is 5432. +
        • +
      • + Username - The username of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Username. +
        • +
      • + Password - The password of your Supabase Database, this was set when you created your Supabase project. If you forgot it you can reset it within your Database Settings +
        • +
      • + Endpoint - This is the endpoint of your Supabase instance under Project Settings -> API. This is used to migrate your files. +
        • +
      • + API Key - This is the key of your Supabase instance under Project Settings -> API. This is used to migrate your files. Make sure to use the hidden service_role key. +
        • +
      +
      2. +
    From 4b5185846b0041c4fe6aac6d745cafc8e408f290 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 16:03:00 +0000 Subject: [PATCH 11/45] Fix migrations index --- app/views/docs/index.phtml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index dac01f024..c4889dee5 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -97,19 +97,10 @@ $cols = [ Migration - - - - From 3b7d63e33e7a96f9a2aa37268836192af6030742 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 17:24:39 +0000 Subject: [PATCH 12/45] Fix language in migration guides for firebase, supabase, and nhost --- app/views/docs/index.phtml | 12 +-- app/views/docs/migration-supabase.phtml | 90 ------------------- ....phtml => migrations-cloud-to-local.phtml} | 4 +- ...rebase.phtml => migrations-firebase.phtml} | 8 +- ....phtml => migrations-local-to-cloud.phtml} | 2 +- ...ion-nhost.phtml => migrations-nhost.phtml} | 48 +++++----- app/views/docs/migrations-supabase.phtml | 88 ++++++++++++++++++ .../{migration.phtml => migrations.phtml} | 32 +++++-- 8 files changed, 151 insertions(+), 133 deletions(-) delete mode 100644 app/views/docs/migration-supabase.phtml rename app/views/docs/{migration-cloud-to-local.phtml => migrations-cloud-to-local.phtml} (92%) rename app/views/docs/{migration-firebase.phtml => migrations-firebase.phtml} (87%) rename app/views/docs/{migration-local-to-cloud.phtml => migrations-local-to-cloud.phtml} (97%) rename app/views/docs/{migration-nhost.phtml => migrations-nhost.phtml} (56%) create mode 100644 app/views/docs/migrations-supabase.phtml rename app/views/docs/{migration.phtml => migrations.phtml} (52%) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index c4889dee5..125f562c6 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -94,13 +94,13 @@ $cols = [
  • Functions
  • - Migration + Migrations diff --git a/app/views/docs/migration-supabase.phtml b/app/views/docs/migration-supabase.phtml deleted file mode 100644 index 871ca85a9..000000000 --- a/app/views/docs/migration-supabase.phtml +++ /dev/null @@ -1,90 +0,0 @@ -

    - Moving your project from Supabase to Appwrite? - Appwrite Migrations can help you streamline the process. - - Here's what you need to know to get started. -

    - -

    Things to keep in mind

    - -
      -
    1. Appwrite will not charge usage during migrations, but Supabase may still incur service charges.
      2. -
    2. Appwrite's Database doesn't support all the features of the postgreSQL database so more advanced postgres centric things things like advanced indexes, postgres functions and scheduling will not be migrated.
      3. -
    3. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
      4. -
    - -

    Supported resource types

    - - - - - - - - - - - - - - - - - - - - - -
    UsersDatabasesDocumentsFilesFunctions
    Supabase✅✅✅✅
    - -

    Migrating to Appwrite from Supabase

    -

    - To begin migrating to Appwrite make sure to read the migration overview - and things to keep in mind sections above. -

    - -
      -
    1. - Create a new project and click on the Migrations tab. -
      2. -
    2. - Click on the Create Migration button and select Supabase as your source. -
      3. -
    3. - Enter the credentials following the instructions below and click Next. -
      4. -
    4. - Select the resources you want to migrate and finally click Start migration to begin the migration process. -
      5. -
    - -

    Credentials

    - -
      -
    1. - Enter all the following credentials from your Supabase project. -
        -
      • - Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. -
        • -
      • - Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host. -
        • -
      • - Port - The port of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Port. By default this is 5432. -
        • -
      • - Username - The username of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Username. -
        • -
      • - Password - The password of your Supabase Database, this was set when you created your Supabase project. If you forgot it you can reset it within your Database Settings -
        • -
      • - Endpoint - This is the endpoint of your Supabase instance under Project Settings -> API. This is used to migrate your files. -
        • -
      • - API Key - This is the key of your Supabase instance under Project Settings -> API. This is used to migrate your files. Make sure to use the hidden service_role key. -
        • -
      -
      2. -
    diff --git a/app/views/docs/migration-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml similarity index 92% rename from app/views/docs/migration-cloud-to-local.phtml rename to app/views/docs/migrations-cloud-to-local.phtml index 3f601a2ec..801d93c0e 100644 --- a/app/views/docs/migration-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -11,10 +11,10 @@
  • Migrations are non-destructive. No data will be deleted or lost in the source project.
    • -

    Migrating to Self-hosted from Cloud

    +

    Migrating to Self-hosted from Cloud

    - To begin migrating to Appwrite Self-hosted, make sure to read the migration overview + To begin migrating to Appwrite Self-hosted, make sure to read the migrations overview and things to keep in mind sections above.

    diff --git a/app/views/docs/migration-firebase.phtml b/app/views/docs/migrations-firebase.phtml similarity index 87% rename from app/views/docs/migration-firebase.phtml rename to app/views/docs/migrations-firebase.phtml index 2d4951cc2..f8c236ea3 100644 --- a/app/views/docs/migration-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -8,10 +8,10 @@

    Things to keep in mind

      -
    1. Appwrite will not charge usage during migrations, but Firebase may still incur service charges.
      2. -
    2. Appwrite migrations only supports Firestore as a database source. Realtime Database is currently not supported.
      3. +
    3. Appwrite will not incur usage charges during migrations, but Firebase may still incur service charges.
      4. +
    4. Appwrite Migrations only supports Firestore as a database source. Realtime Database is currently not supported.
    5. At the moment only top level document migration is supported. Nested documents will not be transferred automatically.
      6. -
    6. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
      7. +
    7. OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.

    Supported resource types

    @@ -40,7 +40,7 @@

    Migrating to Appwrite from Firebase

    - To begin migrating to Appwrite make sure to read the migration overview + To begin migrating to Appwrite make sure to read the migration overview and things to keep in mind sections above.

    diff --git a/app/views/docs/migration-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml similarity index 97% rename from app/views/docs/migration-local-to-cloud.phtml rename to app/views/docs/migrations-local-to-cloud.phtml index e30783d4b..3e19aef74 100644 --- a/app/views/docs/migration-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -13,7 +13,7 @@

    Migrating to Self-hosted from Cloud

    - To begin migrating to self-hosted, make sure to read the migration overview + To begin migrating to self-hosted, make sure to read the migration overview and things to keep in mind sections above.

    diff --git a/app/views/docs/migration-nhost.phtml b/app/views/docs/migrations-nhost.phtml similarity index 56% rename from app/views/docs/migration-nhost.phtml rename to app/views/docs/migrations-nhost.phtml index a556de4a0..0d625eb67 100644 --- a/app/views/docs/migration-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -8,7 +8,7 @@

    Things to keep in mind

      -
    1. Appwrite will not charge usage during migrations, but NHost may still incur service charges.
      2. +
    2. Appwrite will not incur usage charges during migrations, but NHost may still incur service charges.
    3. Appwrite's Database doesn't support all the features of the postgreSQL database so more advanced postgres centric things things like advanced indexes, postgres functions and scheduling will not be migrated.
    4. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
    @@ -39,7 +39,7 @@

    Migrating to Appwrite from NHost

    - To begin migrating to Appwrite make sure to read the migration overview + To begin migrating to Appwrite make sure to read the migration overview and things to keep in mind sections above.

    @@ -59,28 +59,26 @@

    NHost Credentials

    +

    +Enter all the following credentials from your NHost project. +

      -
    1. - Enter all the following credentials from your NHost project. -
        -
      • - Region - The region your NHost project is hosted in. This can be found in your NHost project environment variables as NHOST_REGION. -
        • -
      • - Subdomain - The subdomain of your NHost project. This can be found in your NHost project environment variables as NHOST_SUBDOMAIN. -
        • -
      • - Database - The name of your NHost database. This can be found in your NHost project Database settings. -
        • -
      • - Username - The username of your NHost database. This can be found in your NHost project Database settings. -
        • -
      • - Password - The password of your NHost database. You set this when you created your NHost project, if you don't remember it you can reset it from your NHost project Database settings. -
        • -
      • - Admin Secret - The admin secret of your NHost project. This can be found in your NHost project environment variables as NHOST_ADMIN_SECRET. We use this to transfer your NHost Files to Appwrite. -
        • -
      -
      2. +
    2. + Region - The region your NHost project is hosted in. This can be found in your NHost project environment variables as NHOST_REGION. +
      3. +
    3. + Subdomain - The subdomain of your NHost project. This can be found in your NHost project environment variables as NHOST_SUBDOMAIN. +
      4. +
    4. + Database - The name of your NHost database. This can be found in your NHost project Database settings. +
      5. +
    5. + Username - The username of your NHost database. This can be found in your NHost project Database settings. +
      6. +
    6. + Password - The password of your NHost database. You set this when you created your NHost project, if you don't remember it you can reset it from your NHost project Database settings. +
      7. +
    7. + Admin Secret - The admin secret of your NHost project. This can be found in your NHost project environment variables as NHOST_ADMIN_SECRET. We use this to transfer your NHost files to Appwrite. +
    \ No newline at end of file diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml new file mode 100644 index 000000000..58036bc5e --- /dev/null +++ b/app/views/docs/migrations-supabase.phtml @@ -0,0 +1,88 @@ +

    + Moving your project from Supabase to Appwrite? + Appwrite Migrations can help you streamline the process. + + Here's what you need to know to get started. +

    + +

    Things to keep in mind

    + +
      +
    1. Appwrite will not incur usage charges during migrations, but Supabase may still incur service charges.
      2. +
    2. Appwrite's Databases services supports a different set of features as PostgreSQL. Some features like advanced indexes, Postgres functions and scheduling will not be migrated.
      3. +
    3. OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.
      4. +
    + +

    Supported resource types

    + + + + + + + + + + + + + + + + + + + + + +
    UsersDatabasesDocumentsFilesFunctions
    Supabase✅✅✅✅
    + +

    Migrating to Appwrite from Supabase

    +

    + To begin migrating to Appwrite make sure to read the migration overview + and things to keep in mind sections above. +

    + +
      +
    1. + Create a new project and click on the Migrations tab. +
      2. +
    2. + Click on the Create Migration button and select Supabase as your source. +
      3. +
    3. + Enter the credentials following the instructions below and click Next. +
      4. +
    4. + Select the resources you want to migrate and finally click Start migration to begin the migration process. +
      5. +
    + +

    Credentials

    + +

    Enter all the following credentials from your Supabase project.

    + +
      + +
    1. + Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. +
      2. +
    2. + Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host. +
      3. +
    3. + Port - The port of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Port. By default this is 5432. +
      4. +
    4. + Username - The username of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Username. +
      5. +
    5. + Password - The password of your Supabase Database, this was set when you created your Supabase project. If you forgot your password, you can reset it within Database Settings. +
      6. +
    6. + Endpoint - This is the endpoint of your Supabase instance under Project Settings > API. This is used to migrate your files. +
      7. +
    7. + API Key - This is the key of your Supabase instance under Project Settings > API. This is used to migrate your files. Make sure to use the hidden service_role key. +
      8. +
    diff --git a/app/views/docs/migration.phtml b/app/views/docs/migrations.phtml similarity index 52% rename from app/views/docs/migration.phtml rename to app/views/docs/migrations.phtml index 336689026..d15752efa 100644 --- a/app/views/docs/migration.phtml +++ b/app/views/docs/migrations.phtml @@ -1,6 +1,6 @@

    - Moving your app from another platform to Appwrite? - You can move your app from Firebase, Supabase, NHost, and even other Appwrite projects to another Appwrite project using Migrations. + Ready to migrate your project to Appwrite? + You can move your app from Firebase, Supabase, NHost, and even move between self-hosted and Cloud projects using Migrations. Migrations will automatically move accounts, database documents, and storage files from one source to another.

    @@ -26,7 +26,7 @@ Firebase -

    Migrate from Firebase

    +

    Migrate from Firebase

    @@ -37,7 +37,7 @@ Supabase -

    Migrate from Supabase

    +

    Migrate from Supabase

    @@ -48,7 +48,29 @@ NHost -

    Migrate from NHost

    +

    Migrate from NHost

    + + + + + [IMAGE] + + + Cloud to Self-host + + +

    Migrate from Appwrite Cloud to Self-hosted

    + + + + + [IMAGE] + + + Self-host to Cloud + + +

    Migrate from Self-hosted to Appwrite Cloud

    From 1819b3288c0aff003288fe4d2800b3af035f3a5d Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 17:31:23 +0000 Subject: [PATCH 13/45] Fixed code tags in local to cloud page --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index 3e19aef74..5cfee4cb8 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -6,7 +6,7 @@

    Things to keep in mind

      -
    1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
      2. +
    2. Data transferred by migrations will reset $createdAt and $updatedAt timestamps to the date of the migration.
    3. Your self-hosted Appwrite project must be accessible from the internet for the migration to work.
    4. Migrations are non-destructive. No data will be deleted or lost in the source project.
    From 30bc686cae377cd6597f2cba8125e03bf9ae75ad Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 17:38:51 +0000 Subject: [PATCH 14/45] Fix titles in index --- app/views/docs/index.phtml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index 125f562c6..1d45bff57 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -99,8 +99,8 @@ $cols = [
  •    Firebase
  •    Supabase
  •    NHost
    • -
  •    Cloud to Local
    • -
  •    Local to Cloud
    • +
  •    Cloud to Self-hosted
    • +
  •    Self-hosted to Cloud
    • From 1b974feaec94c8022add7e7b7ca3b3b7fccc7fa5 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 15 Aug 2023 17:42:20 +0000 Subject: [PATCH 15/45] Fix missing ul tag in index --- app/views/docs/index.phtml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index 1d45bff57..ecab000aa 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -101,6 +101,8 @@ $cols = [
  •    NHost
  •    Cloud to Self-hosted
  •    Self-hosted to Cloud
    • +
  •   Security
    • + From fd8e391036e205072c17c7dce011b67eb5653815 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 22 Aug 2023 22:25:10 +0000 Subject: [PATCH 16/45] Don't use images and emojis for Appwrite migration docs --- app/views/docs/index.phtml | 1 - app/views/docs/migrations-firebase.phtml | 10 +++++----- app/views/docs/migrations-nhost.phtml | 10 +++++----- app/views/docs/migrations-supabase.phtml | 10 +++++----- app/views/docs/migrations.phtml | 16 ---------------- 5 files changed, 15 insertions(+), 32 deletions(-) diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index ecab000aa..ec9819fbf 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -101,7 +101,6 @@ $cols = [
  •    NHost
  •    Cloud to Self-hosted
  •    Self-hosted to Cloud
    • -
  •   Security
    • diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index f8c236ea3..0aacc6bc0 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -29,11 +29,11 @@ Firebase - ✅ - ✅ - ✅ - ✅ - + supported + supported + supported + supported + not supported diff --git a/app/views/docs/migrations-nhost.phtml b/app/views/docs/migrations-nhost.phtml index 0d625eb67..e6c84a22b 100644 --- a/app/views/docs/migrations-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -28,11 +28,11 @@ NHost - ✅ - ✅ - ✅ - ✅ - + supported + supported + supported + supported + not supported diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index 58036bc5e..02b0bb132 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -28,11 +28,11 @@ Supabase - ✅ - ✅ - ✅ - ✅ - + supported + supported + supported + supported + not supported diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index d15752efa..53dc3eae5 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -12,16 +12,12 @@ - - @@ -30,9 +26,6 @@ - @@ -41,9 +34,6 @@ - @@ -52,9 +42,6 @@ - @@ -63,9 +50,6 @@ - From e6f2aace423816b64e0f0bafa050a9dd82ef8f6f Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 22 Aug 2023 22:49:21 +0000 Subject: [PATCH 17/45] Reformat support table to be in overview --- app/views/docs/migrations-firebase.phtml | 24 --------- app/views/docs/migrations-nhost.phtml | 24 --------- app/views/docs/migrations-supabase.phtml | 24 --------- app/views/docs/migrations.phtml | 65 +++++++++++++++--------- 4 files changed, 42 insertions(+), 95 deletions(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index 0aacc6bc0..a8fdc3fed 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -14,30 +14,6 @@
  • OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.
    • -

    Supported resource types

    -
    Source
    - [IMAGE] - Firebase
    - [IMAGE] - Supabase
    - [IMAGE] - NHost
    - [IMAGE] - Cloud to Self-host
    - [IMAGE] - Self-host to Cloud
    - - - - - - - - - - - - - - - - - - - - -
    UsersDatabasesDocumentsFilesFunctions
    Firebasesupportedsupportedsupportedsupportednot supported
    -

    Migrating to Appwrite from Firebase

    To begin migrating to Appwrite make sure to read the migration overview diff --git a/app/views/docs/migrations-nhost.phtml b/app/views/docs/migrations-nhost.phtml index e6c84a22b..ca9aed1d5 100644 --- a/app/views/docs/migrations-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -13,30 +13,6 @@

  • OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
    • -

    Supported resource types

    - - - - - - - - - - - - - - - - - - - - - -
    UsersDatabasesDocumentsFilesFunctions
    NHostsupportedsupportedsupportedsupportednot supported
    -

    Migrating to Appwrite from NHost

    To begin migrating to Appwrite make sure to read the migration overview diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index 02b0bb132..754445ad0 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -13,30 +13,6 @@

  • OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.
    • -

    Supported resource types

    - - - - - - - - - - - - - - - - - - - - - -
    UsersDatabasesDocumentsFilesFunctions
    Supabasesupportedsupportedsupportedsupportednot supported
    -

    Migrating to Appwrite from Supabase

    To begin migrating to Appwrite make sure to read the migration overview diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index 53dc3eae5..a42226e95 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -1,5 +1,5 @@

    - Ready to migrate your project to Appwrite? + If you're looking to migrate existing projects to Appwrite, Migrations can help you make the move more quickly. You can move your app from Firebase, Supabase, NHost, and even move between self-hosted and Cloud projects using Migrations. Migrations will automatically move accounts, database documents, and storage files from one source to another.

    @@ -12,50 +12,64 @@ - - + + + + + + - + + + + + - + + + + + - + + + + + - + + + + + - + + + + +
    SourceSourceUsersDatabasesDocumentsFilesFunctions
    - Firebase - -

    Migrate from Firebase

    +

    Firebase

    		supportedsupportedpartialsupported
    - Supabase - -

    Migrate from Supabase

    +

    Supabase

    		supportedsupportedpartialsupported
    - NHost - -

    Migrate from NHost

    +

    NHost

    		supportedsupportedpartialsupported
    - Cloud to Self-host - -

    Migrate from Appwrite Cloud to Self-hosted

    +

    Cloud to Self-hosted

    		supportedsupportedsupportedsupportedsupported
    - Self-host to Cloud - -

    Migrate from Self-hosted to Appwrite Cloud

    +

    Self-hosted to Cloud

    		supportedsupportedsupportedsupportedsupported
    @@ -64,4 +78,9 @@

    Migrations cannot transfer all data perfectly, so certain fields, such as $createdAt and $updatedAt, may not be transferred. More information can be found on the migration page for each source. +

    + +

    + Migrations help you jump start your move, but because each product is unique, complex databases and product unique features like functions need to be migrated manually. + We also recommend you carefully validate permissions and data integrity when moving between platforms.

    \ No newline at end of file From 7de3dd7d998566362a46afa9c1a8a81255ac48a6 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 22 Aug 2023 22:50:11 +0000 Subject: [PATCH 18/45] Instead of not support, call it manual --- app/views/docs/migrations.phtml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index a42226e95..e5469750d 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -29,7 +29,7 @@ supported partial supported - + manual @@ -39,7 +39,7 @@ supported partial supported - + manual @@ -49,7 +49,7 @@ supported partial supported - + manual From 1d465e5fec72f39f457748d8e963f6d6d4134226 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Tue, 22 Aug 2023 22:54:02 +0000 Subject: [PATCH 19/45] Change partial to yellow --- app/views/docs/migrations.phtml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index e5469750d..d51e3709f 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -27,7 +27,7 @@ supported supported - partial + partial supported manual @@ -37,7 +37,7 @@ supported supported - partial + partial supported manual @@ -47,7 +47,7 @@ supported supported - partial + partial supported manual From 2b868da2bf7e49cce4583c5082ec8f1287fb9fb7 Mon Sep 17 00:00:00 2001 From: Bradley Schofield Date: Thu, 24 Aug 2023 11:01:08 +0100 Subject: [PATCH 20/45] Add alot more details around service account key creation --- app/views/docs/migrations-firebase.phtml | 158 +++++++++++++++++++---- 1 file changed, 130 insertions(+), 28 deletions(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index f8c236ea3..67cbd68e9 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -1,7 +1,7 @@

    Moving your project from Firebase to Appwrite? Appwrite Migrations can help you streamline the process. - + Here's what you need to know to get started.

    @@ -16,34 +16,34 @@

    Supported resource types

    - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + +
    UsersDatabasesDocumentsFilesFunctions
    Firebase✅✅✅✅
    UsersDatabasesDocumentsFilesFunctions
    Firebase✅✅✅✅

    Migrating to Appwrite from Firebase

    - To begin migrating to Appwrite make sure to read the migration overview + To begin migrating to Appwrite make sure to read the migration overview and things to keep in mind sections above.

    - +
    1. Create a new project and click on the Migrations tab. @@ -52,7 +52,7 @@ Click on the Create Migration button and select Firebase as your source.
    2. - Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. + Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. See the Cloud and Self-hosting sections for details.
    3. @@ -79,12 +79,114 @@ Click the gear icon to access your Project Settings.
    4. - Click Service Accounts, then Generate New Private Key. Don't share this key with anyone! + Click on Service Accounts, then click on the Manage service account permissions link redirecting you to the Google Cloud Console.
    5. - Once you've downloaded your private key, head back to Appwrite and click Manual Authentication. + Click on Create Service Account, give it any name, id and description you want, then click Continue.
    6. - Upload the JSON private key and follow the wizard. + Next you'll be prompted to grant the service account roles, grant the following roles:
      7. -
    + + + + + + + + + + + + + + + + + +
    RoleReason
    Firebase ViewerRead access to your entire Firebase project including Database and Storage
    Identity Toolkit ViewerRead access to your users including their hash config
    +
  • If you prefer to create a custom role, you can use the following permissions:
    • + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    PermissionReason
    datastore.databases.getRead access to your Firestore database
    datastore.databases.listRead access to your Firestore database
    datastore.entities.getRead access to your Firestore database's documents
    datastore.entities.listRead access to your Firestore database's documents
    datastore.indexes.getRead access to your Firestore database's indexes
    datastore.indexes.listRead access to your Firestore database's indexes
    firebaseauth.configs.getRead access to your Firebase project's authentication configs
    firebaseauth.configs.getHashConfigRead access to your Firebase project's authentication configs including hash salt
    firebaseauth.configs.getSecretRead access to your Firebase project's authentication configs including secret
    firebaseauth.users.getRead access to your Firebase project's users
    identitytoolkit.tenants.getRead access to your Firebase project's users
    identitytoolkit.tenants.listRead access to your Firebase project's users
    storage.buckets.getRead access to your Firebase project's storage buckets
    storage.buckets.listRead access to your Firebase project's storage buckets
    storage.objects.getRead access to your Firebase project's storage objects
    storage.objects.listRead access to your Firebase project's storage objects
    +
  • + Click Done to create the service account. After that you'll be redirected back to the service accounts page. Select the service account you just created and click Keys. +
    • +
  • + Click Add Key and select Create new key. Select JSON as the key type and click Create. This will download a JSON file to your computer. +
    • +
  • + Upload the JSON file to Appwrite and follow the migration wizard. +
    • + \ No newline at end of file From f7fe08ed2e4eb7f0edeb74dea6aeea063d475166 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 11:51:36 -0400 Subject: [PATCH 21/45] Update app/views/docs/migrations-firebase.phtml --- app/views/docs/migrations-firebase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index 893659197..cf575693e 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -58,7 +58,7 @@ Click on Service Accounts, then click on the Manage service account permissions link redirecting you to the Google Cloud Console.
  • - Click on Create Service Account, give it any name, id and description you want, then click Continue. + Click on Create Service Account, give it a name, id and description you want, then click Continue.
  • Next you'll be prompted to grant the service account roles, grant the following roles: From 255224e3bfaaa36b219f548955bc0ea72030222f Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 11:51:41 -0400 Subject: [PATCH 22/45] Update app/views/docs/migrations-firebase.phtml --- app/views/docs/migrations-firebase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index cf575693e..c7a40ab3a 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -61,7 +61,7 @@ Click on Create Service Account, give it a name, id and description you want, then click Continue.
  • - Next you'll be prompted to grant the service account roles, grant the following roles: + Next you'll be prompted to grant the service account roles. You need to grant the following roles.
    • From d33d2230e3c66c3b98428cdd81db0b73304363c2 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 11:51:46 -0400 Subject: [PATCH 23/45] Update app/views/docs/migrations-firebase.phtml --- app/views/docs/migrations-firebase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index c7a40ab3a..e131a7826 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -73,7 +73,7 @@ - + From 6f67e62e39902e51efc8924839c801f8ca77e287 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 11:51:51 -0400 Subject: [PATCH 24/45] Update app/views/docs/migrations-firebase.phtml --- app/views/docs/migrations-firebase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index e131a7826..cb27cd23b 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -77,7 +77,7 @@ - +
    Firebase ViewerRead access to your entire Firebase project including Database and Storage
    		Read access to your entire Firebase project including Database and Storage.
    Identity Toolkit Viewer
    Identity Toolkit ViewerRead access to your users including their hash config
    		Read access to your users including their hash config.
    From 124826a67e84e87a08917c78a3ddfeeb78bdfe29 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 16:08:08 +0000 Subject: [PATCH 25/45] fix some style and grammar --- .../docs/migrations-cloud-to-local.phtml | 2 +- app/views/docs/migrations-firebase.phtml | 47 ++++++++++--------- .../docs/migrations-local-to-cloud.phtml | 2 +- 3 files changed, 28 insertions(+), 23 deletions(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index 801d93c0e..743efb54b 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -1,5 +1,5 @@

    - Moving to a self-hosted instance? We've got you covered. + If you're moving your projects from Appwrite Cloud to self-hosted, we've got you covered. Migrations makes it as easy as a couple clicks to move all of your Appwrite Cloud project data to a self-hosted instance.

    diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index cb27cd23b..c5d234175 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -36,13 +36,15 @@ -

    Appwrite Cloud

    +

    Migrate to Cloud

    To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically discover your Firebase projects. Simply select the source project and follow the migration wizard.

    -

    Migrating to Appwrite Self-Hosted

    +

    After completing the migration wizard, migration will begin. Return to step 4 of the migration steps.

    + +

    Migrating to Self-Hosted

    If you are self-hosting Appwrite you will need to create a service account in your Firebase project and download the JSON file.

    @@ -63,7 +65,7 @@
  • Next you'll be prompted to grant the service account roles. You need to grant the following roles.
    • - +
    @@ -81,8 +83,8 @@
    Role
    -
  • If you prefer to create a custom role, you can use the following permissions:
    • - +
  • If you prefer to create a custom role, you can use the following permissions.
    • +
    @@ -92,67 +94,67 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
    Permission
    datastore.databases.getRead access to your Firestore databaseRead access to your Firestore database.
    datastore.databases.listRead access to your Firestore databaseRead access to your Firestore database.
    datastore.entities.getRead access to your Firestore database's documentsRead access to your Firestore database's documents.
    datastore.entities.listRead access to your Firestore database's documentsRead access to your Firestore database's documents.
    datastore.indexes.getRead access to your Firestore database's indexesRead access to your Firestore database's indexes.
    datastore.indexes.listRead access to your Firestore database's indexesRead access to your Firestore database's indexes.
    firebaseauth.configs.getRead access to your Firebase project's authentication configsRead access to your Firebase project's authentication configs.
    firebaseauth.configs.getHashConfigRead access to your Firebase project's authentication configs including hash saltRead access to your Firebase project's authentication configs including hash salt.
    firebaseauth.configs.getSecretRead access to your Firebase project's authentication configs including secretRead access to your Firebase project's authentication configs including secret.
    firebaseauth.users.getRead access to your Firebase project's usersRead access to your Firebase project's users.
    identitytoolkit.tenants.getRead access to your Firebase project's usersRead access to your Firebase project's users.
    identitytoolkit.tenants.listRead access to your Firebase project's usersRead access to your Firebase project's users.
    storage.buckets.getRead access to your Firebase project's storage bucketsRead access to your Firebase project's storage buckets.
    storage.buckets.listRead access to your Firebase project's storage bucketsRead access to your Firebase project's storage buckets.
    storage.objects.getRead access to your Firebase project's storage objectsRead access to your Firebase project's storage objects.
    storage.objects.listRead access to your Firebase project's storage objectsRead access to your Firebase project's storage objects.
    @@ -165,4 +167,7 @@
  • Upload the JSON file to Appwrite and follow the migration wizard.
    • +
  • + After completing the migration wizard, migration will begin. Return to step 4 of the migration steps. +
    • \ No newline at end of file diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index 5cfee4cb8..96cd51ec3 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -1,5 +1,5 @@

    - Making the move to Appwrite Cloud? We've got your back. + If you're moving your self-hosted projects to Appwrite Cloud, we've got your back. Migrations makes it as easy as a couple clicks to move all of your self-hosted project data to a Cloud instance.

    From eaa9683820bde906933c40c4500dcb77f15ffd8f Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Thu, 24 Aug 2023 12:12:27 -0400 Subject: [PATCH 26/45] Update app/views/docs/migrations-supabase.phtml Co-authored-by: Bradley Schofield --- app/views/docs/migrations-supabase.phtml | 3 --- 1 file changed, 3 deletions(-) diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index 754445ad0..e5b789ebd 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -40,9 +40,6 @@
      -
    1. - Region - The region your Supabase project is hosted in. This can be found in your Supabase project environment variables as Supabase_REGION. -
    2. Host - The host of your Supabase Database, this can be found in your Supabase project settings under Database Settings and Host.
      3. From f6dff91336e60e90ef216ab7d343fbd66e9f2a5f Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:30:55 -0400 Subject: [PATCH 27/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index 743efb54b..8fb11b0cb 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -20,7 +20,7 @@

      Steps on Your Cloud Project

        -
      1. Navigate to your Appwrite Cloud Console and click on the Migrations tab.
        2. +
      2. Navigate to your Appwrite Cloud Console and click on the Migrations tab in Project Settings.
      3. Click Export to Self-hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
      4. Optionally, tell us about why you're moving to self-hosted.
      5. After clicking Continue, you'll be directed back to your self-hosted project to complete the process.
        6. From 54300083b3e7b8fb12cf4b7a5870ca985dab3640 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:31:04 -0400 Subject: [PATCH 28/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index 8fb11b0cb..184e43bd1 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -23,7 +23,7 @@
      6. Navigate to your Appwrite Cloud Console and click on the Migrations tab in Project Settings.
      7. Click Export to Self-hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
      8. Optionally, tell us about why you're moving to self-hosted.
        9. -
      9. After clicking Continue, you'll be directed back to your self-hosted project to complete the process.
        10. +
      10. After clicking Continue, you'll be redirected to your self-hosted project to complete the process.

      Steps on Your Self-hosted Project

      From 635ee8dbeadc61da5cf37b9802b5bbe406988757 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:31:19 -0400 Subject: [PATCH 29/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index 184e43bd1..c66644803 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -18,7 +18,7 @@ and things to keep in mind sections above.

      -

      Steps on Your Cloud Project

      +

      Steps in Cloud Console

      1. Navigate to your Appwrite Cloud Console and click on the Migrations tab in Project Settings.
      2. Click Export to Self-hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
        3. From 47dd217e4365b9b6ce5a3046054cb7c89a81b24a Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:31:32 -0400 Subject: [PATCH 30/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index c66644803..abfb8e673 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -26,7 +26,7 @@
      3. After clicking Continue, you'll be redirected to your self-hosted project to complete the process.
      -

      Steps on Your Self-hosted Project

      +

      Steps in Self-hosted Console

      1. Once redirected to your self-hosted project, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
      2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
        3. From 3cdd52d888b82dcb4bbb8b4ae6c1e4fbe73ba454 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:31:58 -0400 Subject: [PATCH 31/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index abfb8e673..c242905ad 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -28,7 +28,7 @@

        Steps in Self-hosted Console

          -
        1. Once redirected to your self-hosted project, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
          2. +
        2. Once redirected to your self-hosted server, you'll be prompted to select a project. If you have multiple organizations, you will also be asked to pick one. You can migrate to an existing project or create a new one.
        3. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
        4. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
        \ No newline at end of file From 98f2b36efd36f33d2fabdecfdb7435efd6165707 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:32:13 -0400 Subject: [PATCH 32/45] Update app/views/docs/migrations-cloud-to-local.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-cloud-to-local.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-cloud-to-local.phtml b/app/views/docs/migrations-cloud-to-local.phtml index c242905ad..6c012e1ef 100644 --- a/app/views/docs/migrations-cloud-to-local.phtml +++ b/app/views/docs/migrations-cloud-to-local.phtml @@ -30,5 +30,5 @@
        1. Once redirected to your self-hosted server, you'll be prompted to select a project. If you have multiple organizations, you will also be asked to pick one. You can migrate to an existing project or create a new one.
        2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
          3. -
        3. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
          4. +
        4. Click Start migration to begin the migration process. You do not need to keep the Appwrite Console open through the process.
        \ No newline at end of file From 09607691e7824b53393e776569ed81fed8c73624 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:32:48 -0400 Subject: [PATCH 33/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index 96cd51ec3..e69a47ff0 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -11,7 +11,7 @@
      3. Migrations are non-destructive. No data will be deleted or lost in the source project.
      -

      Migrating to Self-hosted from Cloud

      +

      Migrating to Cloud from Self-hosted

      To begin migrating to self-hosted, make sure to read the migration overview and things to keep in mind sections above. From b8d7cafd11c538ab25b7e4977dbb8c81317cd9cf Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:33:03 -0400 Subject: [PATCH 34/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index e69a47ff0..3b51000a9 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -17,7 +17,7 @@ and things to keep in mind sections above.

      -

      Steps on Your Self-hosted Project

      +

      Steps in Self-hosted Console

      1. Navigate to your self-hosted project's console and click on the Migrations tab.
        2. From d21952e2340b8a78596ab3b4764143ad28cb60ab Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:33:12 -0400 Subject: [PATCH 35/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index 3b51000a9..4f6e8ac78 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -25,7 +25,7 @@
      2. You will complete the migration on Appwrite Cloud.
      -

      Steps on Your Cloud Project

      +

      Steps in Cloud Console

      1. Once redirected to Appwrite Cloud, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
      2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
        3. From d18687646ba34a710c55ec7d7fa4daa361d31e34 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:33:19 -0400 Subject: [PATCH 36/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index 4f6e8ac78..f1db09fb4 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -20,7 +20,7 @@

        Steps in Self-hosted Console

          -
        1. Navigate to your self-hosted project's console and click on the Migrations tab.
          2. +
        2. Navigate to your self-hosted project's console and click on the Migrations tab in Project Settings.
        3. Click Deploy to cloud, you will be redirected to Appwrite Cloud.
        4. You will complete the migration on Appwrite Cloud.
        From 3b6ca9aee33137e745fa35d70688ff68b2f8beb8 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:33:41 -0400 Subject: [PATCH 37/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index f1db09fb4..bf2efd78c 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -21,7 +21,7 @@
        1. Navigate to your self-hosted project's console and click on the Migrations tab in Project Settings.
          2. -
        2. Click Deploy to cloud, you will be redirected to Appwrite Cloud.
          3. +
        3. Click Deploy to cloud, and you will be redirected to Appwrite Cloud.
        4. You will complete the migration on Appwrite Cloud.
        From 70d285eb1b328420a869c22eeb39e51663bd5962 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:34:53 -0400 Subject: [PATCH 38/45] Update app/views/docs/migrations-local-to-cloud.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-local-to-cloud.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-local-to-cloud.phtml b/app/views/docs/migrations-local-to-cloud.phtml index bf2efd78c..9040dafa1 100644 --- a/app/views/docs/migrations-local-to-cloud.phtml +++ b/app/views/docs/migrations-local-to-cloud.phtml @@ -27,7 +27,7 @@

        Steps in Cloud Console

          -
        1. Once redirected to Appwrite Cloud, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
          2. +
        2. Once redirected to Appwrite Cloud, you'll be prompted to select a project. If you have multiple organizations, you will also be asked to pick one. You can migrate to an existing project or create a new one.
        3. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
        4. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
        From 70518866774a5be3262c8faa455d433b5ff80233 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:36:04 -0400 Subject: [PATCH 39/45] Update app/views/docs/migrations.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations.phtml | 1 + 1 file changed, 1 insertion(+) diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index d51e3709f..8f1b98d8e 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -1,6 +1,7 @@

        If you're looking to migrate existing projects to Appwrite, Migrations can help you make the move more quickly. You can move your app from Firebase, Supabase, NHost, and even move between self-hosted and Cloud projects using Migrations. + You can also use Migrations to move between two self-hosted instances or even to duplicate project on the same instance. Migrations will automatically move accounts, database documents, and storage files from one source to another.

        From 645eb610e20c31003a5e4739d70c5bdb37e49e2a Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:36:14 -0400 Subject: [PATCH 40/45] Update app/views/docs/migrations.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index 8f1b98d8e..6e3e09661 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -82,6 +82,6 @@

        - Migrations help you jump start your move, but because each product is unique, complex databases and product unique features like functions need to be migrated manually. + Migrations help you jump start your move, but because each product is unique, complex databases and product unique features like functions might need to be migrated manually. We also recommend you carefully validate permissions and data integrity when moving between platforms.

        \ No newline at end of file From 6ddde09aaa2b391f2d2aa7b253ac3cef0dc10332 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:36:40 -0400 Subject: [PATCH 41/45] Update app/views/docs/migrations-nhost.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-nhost.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-nhost.phtml b/app/views/docs/migrations-nhost.phtml index ca9aed1d5..0c48071da 100644 --- a/app/views/docs/migrations-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -21,7 +21,7 @@
        1. - Create a new project and click on the Migrations tab. + Create a new project and click on the Migrations tab in Project Settings.
        2. Click on the Create Migration button and select NHost as your source. From 7e06a3068ca577f62e7c4748544214a8a88d5050 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:36:49 -0400 Subject: [PATCH 42/45] Update app/views/docs/migrations-supabase.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-supabase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index e5b789ebd..09ecd1fd3 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -21,7 +21,7 @@
          1. - Create a new project and click on the Migrations tab. + Create a new project and click on the Migrations tab in Project Settings.
          2. Click on the Create Migration button and select Supabase as your source. From bf58e0f0ced58b2ca6ae12d3ecdca9176d83e152 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 10:37:02 -0400 Subject: [PATCH 43/45] Update app/views/docs/migrations-firebase.phtml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Matej Bačo --- app/views/docs/migrations-firebase.phtml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index c5d234175..999147a8d 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -22,7 +22,7 @@
            1. - Create a new project and click on the Migrations tab. + Create a new project and click on the Migrations tab in Project Settings.
            2. Click on the Create Migration button and select Firebase as your source. From 2e5216e28024ff25e85af015ba1a6a25d7966724 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 16:37:03 +0000 Subject: [PATCH 44/45] Resolve conflicts with upstream --- app/views/docs/index.phtml | 4 +- .../migrations-cloud-to-self-hosted.phtml | 34 +++++++++++++++++ app/views/docs/migrations-firebase.phtml | 5 ++- app/views/docs/migrations-nhost.phtml | 3 +- .../migrations-self-hosted-to-cloud.phtml | 38 +++++++++++++++++++ app/views/docs/migrations-supabase.phtml | 3 +- app/views/docs/migrations.phtml | 9 +++-- 7 files changed, 87 insertions(+), 9 deletions(-) create mode 100644 app/views/docs/migrations-cloud-to-self-hosted.phtml create mode 100644 app/views/docs/migrations-self-hosted-to-cloud.phtml diff --git a/app/views/docs/index.phtml b/app/views/docs/index.phtml index ec9819fbf..b57eb9a43 100644 --- a/app/views/docs/index.phtml +++ b/app/views/docs/index.phtml @@ -99,8 +99,8 @@ $cols = [
            3.    Firebase
            4.    Supabase
            5.    NHost
              6. -
            6.    Cloud to Self-hosted
              7. -
            7.    Self-hosted to Cloud
              8. +
            8.    Cloud to Self-hosted
              9. +
            9.    Self-hosted to Cloud
              10. diff --git a/app/views/docs/migrations-cloud-to-self-hosted.phtml b/app/views/docs/migrations-cloud-to-self-hosted.phtml new file mode 100644 index 000000000..801d93c0e --- /dev/null +++ b/app/views/docs/migrations-cloud-to-self-hosted.phtml @@ -0,0 +1,34 @@ +

              + Moving to a self-hosted instance? We've got you covered. + Migrations makes it as easy as a couple clicks to move all of your Appwrite Cloud project data to a self-hosted instance. +

              + +

              Things to keep in mind

              + +
                +
              1. Data transferred by migrations will reset `$createdAt` and `$updatedAt` timestamps to the date of the migration.
                2. +
              2. Your self-hosted Appwrite project must be accessible from the internet for the migration to work.
                3. +
              3. Migrations are non-destructive. No data will be deleted or lost in the source project.
                4. +
              + +

              Migrating to Self-hosted from Cloud

              + +

              + To begin migrating to Appwrite Self-hosted, make sure to read the migrations overview + and things to keep in mind sections above. +

              + +

              Steps on Your Cloud Project

              +
                +
              1. Navigate to your Appwrite Cloud Console and click on the Migrations tab.
                2. +
              2. Click Export to Self-hosted, you will be prompted to input the URL of your self-hosted Appwrite project.
                3. +
              3. Optionally, tell us about why you're moving to self-hosted.
                4. +
              4. After clicking Continue, you'll be directed back to your self-hosted project to complete the process.
                5. +
              + +

              Steps on Your Self-hosted Project

              +
                +
              1. Once redirected to your self-hosted project, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
                2. +
              2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
                3. +
              3. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
                4. +
              \ No newline at end of file diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index 999147a8d..f16efc879 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -10,8 +10,9 @@
              1. Appwrite will not incur usage charges during migrations, but Firebase may still incur service charges.
              2. Appwrite Migrations only supports Firestore as a database source. Realtime Database is currently not supported.
                3. -
              3. At the moment only top level document migration is supported. Nested documents will not be transferred automatically.
                4. -
              4. OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.
                5. +
              5. At the moment only top level document migration is supported. Nested documents will not be migrated automatically.
                6. +
              6. OAuth users will not be migrated because the sessions are managed by the third-party OAuth provider. Users will need to re-authenticate with your OAuth provider after the migration is complete.
                7. +
              7. Functions are not automatically migrated because of syntax and runtime differences.

              Migrating to Appwrite from Firebase

              diff --git a/app/views/docs/migrations-nhost.phtml b/app/views/docs/migrations-nhost.phtml index 0c48071da..20a8edef2 100644 --- a/app/views/docs/migrations-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -10,7 +10,8 @@
              1. Appwrite will not incur usage charges during migrations, but NHost may still incur service charges.
              2. Appwrite's Database doesn't support all the features of the postgreSQL database so more advanced postgres centric things things like advanced indexes, postgres functions and scheduling will not be migrated.
                3. -
              3. OAuth users will not be transferred. You will need to re-authenticate with your OAuth provider after the migration is complete.
                4. +
              4. OAuth users will not be migrated because the sessions are managed by the third-party OAuth provider. Users will need to re-authenticate with your OAuth provider after the migration is complete.
                5. +
              5. Functions are not automatically migrated because of syntax and runtime differences.

              Migrating to Appwrite from NHost

              diff --git a/app/views/docs/migrations-self-hosted-to-cloud.phtml b/app/views/docs/migrations-self-hosted-to-cloud.phtml new file mode 100644 index 000000000..5cfee4cb8 --- /dev/null +++ b/app/views/docs/migrations-self-hosted-to-cloud.phtml @@ -0,0 +1,38 @@ +

              + Making the move to Appwrite Cloud? We've got your back. + Migrations makes it as easy as a couple clicks to move all of your self-hosted project data to a Cloud instance. +

              + +

              Things to keep in mind

              + +
                +
              1. Data transferred by migrations will reset $createdAt and $updatedAt timestamps to the date of the migration.
                2. +
              2. Your self-hosted Appwrite project must be accessible from the internet for the migration to work.
                3. +
              3. Migrations are non-destructive. No data will be deleted or lost in the source project.
                4. +
              + +

              Migrating to Self-hosted from Cloud

              +

              + To begin migrating to self-hosted, make sure to read the migration overview + and things to keep in mind sections above. +

              + +

              Steps on Your Self-hosted Project

              + +
                +
              1. Navigate to your self-hosted project's console and click on the Migrations tab.
                2. +
              2. Click Deploy to cloud, you will be redirected to Appwrite Cloud.
                3. +
              3. You will complete the migration on Appwrite Cloud.
                4. +
              + +

              Steps on Your Cloud Project

              +
                +
              1. Once redirected to Appwrite Cloud, you'll be prompted to select an organization and a project. You can migrate to an existing project or create a new one.
                2. +
              2. Select the data you wish to migrate. You can choose among accounts, databases, documents, files, and functions.
                3. +
              3. Click Start migration to start the migration process. You do not need to keep the Appwrite Console open through the process.
                4. +
              + +
              +

              Keep in mind

              +

              Your Self-hosted instance will generate a API Key in the background to pass to Cloud. You can revoke this key after the migration process is complete.

              +
              \ No newline at end of file diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index 09ecd1fd3..dedbcbcb7 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -10,7 +10,8 @@
              1. Appwrite will not incur usage charges during migrations, but Supabase may still incur service charges.
              2. Appwrite's Databases services supports a different set of features as PostgreSQL. Some features like advanced indexes, Postgres functions and scheduling will not be migrated.
                3. -
              3. OAuth users will not be transferred. Users will need to re-authenticate with your OAuth provider after the migration is complete.
                4. +
              4. OAuth users will not be migrated because the sessions are managed by the third-party OAuth provider. Users will need to re-authenticate with your OAuth provider after the migration is complete.
                5. +
              5. Functions are not automatically migrated because of syntax and runtime differences.

              Migrating to Appwrite from Supabase

              diff --git a/app/views/docs/migrations.phtml b/app/views/docs/migrations.phtml index 6e3e09661..e130ae472 100644 --- a/app/views/docs/migrations.phtml +++ b/app/views/docs/migrations.phtml @@ -7,7 +7,10 @@

              Supported sources

              - You can transfer from these sources to an Appwrite project. + You can transfer from these sources to an Appwrite project. + Resources marked supported are migrated automatically. + Resources marked partial can be migrated, but with limitations or caveats, check the guide for each source to learn more. + Resources marked manual require manual migration.

              @@ -54,7 +57,7 @@ @@ -64,7 +67,7 @@ From eb9d20aa77914b85e99288bcc4888a30110e9a06 Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 25 Aug 2023 16:51:04 +0000 Subject: [PATCH 45/45] Address matej's comments --- app/views/docs/migrations-firebase.phtml | 26 +++--------------------- app/views/docs/migrations-nhost.phtml | 3 +++ app/views/docs/migrations-supabase.phtml | 3 +++ 3 files changed, 9 insertions(+), 23 deletions(-) diff --git a/app/views/docs/migrations-firebase.phtml b/app/views/docs/migrations-firebase.phtml index f16efc879..2c351d599 100644 --- a/app/views/docs/migrations-firebase.phtml +++ b/app/views/docs/migrations-firebase.phtml @@ -28,29 +28,6 @@
            10. Click on the Create Migration button and select Firebase as your source.
              11. -
            11. - Depending on where your Appwrite project is hosted, you'll need to use different methods to authorize with Firebase. - See the Cloud and Self-hosting sections for details. -
              12. -
            12. - Finally, add the platforms for your Web, Flutter, Android, and iOS apps. -
              13. - - -

              Migrate to Cloud

              -

              - To simplify the migration process we have created an OAuth application that will allow you to sign in with Google and automatically - discover your Firebase projects. Simply select the source project and follow the migration wizard. -

              - -

              After completing the migration wizard, migration will begin. Return to step 4 of the migration steps.

              - -

              Migrating to Self-Hosted

              -

              - If you are self-hosting Appwrite you will need to create a service account in your Firebase project and download the JSON file. -

              - -
              1. Navigate to your Firebase console.
                2. @@ -171,4 +148,7 @@
              2. After completing the migration wizard, migration will begin. Return to step 4 of the migration steps.
                3. +
              3. + Finally, add the platforms for your Web, Flutter, Android, and iOS apps. +
              \ No newline at end of file diff --git a/app/views/docs/migrations-nhost.phtml b/app/views/docs/migrations-nhost.phtml index 20a8edef2..7558fe9b5 100644 --- a/app/views/docs/migrations-nhost.phtml +++ b/app/views/docs/migrations-nhost.phtml @@ -33,6 +33,9 @@
            13. Select the resources you want to migrate and finally click Start migration to begin the migration process.
              14. +
            14. + Finally, add the platforms for your Web, Flutter, Android, and iOS apps. +

              15. NHost Credentials

              diff --git a/app/views/docs/migrations-supabase.phtml b/app/views/docs/migrations-supabase.phtml index dedbcbcb7..8ff4a7bca 100644 --- a/app/views/docs/migrations-supabase.phtml +++ b/app/views/docs/migrations-supabase.phtml @@ -33,6 +33,9 @@
            15. Select the resources you want to migrate and finally click Start migration to begin the migration process.
              16. +
            16. + Finally, add the platforms for your Web, Flutter, Android, and iOS apps. +

              17. Credentials

              -

              Cloud to Self-hosted

              +

              Cloud to Self-hosted

              		 supported supported
              -

              Self-hosted to Cloud

              +

              Self-hosted to Cloud

              		 supported supported