diff --git a/.gitbook/assets/Screenshot_20240411-104804_Anytype3.png b/.gitbook/assets/Screenshot_20240411-104804_Anytype3.png new file mode 100644 index 0000000..6c624a6 Binary files /dev/null and b/.gitbook/assets/Screenshot_20240411-104804_Anytype3.png differ diff --git a/.gitbook/assets/Screenshot_20240411-104810_Anytype2.png b/.gitbook/assets/Screenshot_20240411-104810_Anytype2.png new file mode 100644 index 0000000..25280d4 Binary files /dev/null and b/.gitbook/assets/Screenshot_20240411-104810_Anytype2.png differ diff --git a/.gitbook/assets/image (49).png b/.gitbook/assets/image (49).png new file mode 100644 index 0000000..eadc253 Binary files /dev/null and b/.gitbook/assets/image (49).png differ diff --git a/.gitbook/assets/image (50).png b/.gitbook/assets/image (50).png new file mode 100644 index 0000000..377c44e Binary files /dev/null and b/.gitbook/assets/image (50).png differ diff --git a/.gitbook/assets/image (51).png b/.gitbook/assets/image (51).png new file mode 100644 index 0000000..6c30315 Binary files /dev/null and b/.gitbook/assets/image (51).png differ diff --git a/.gitbook/assets/image (52).png b/.gitbook/assets/image (52).png new file mode 100644 index 0000000..2cb4a32 Binary files /dev/null and b/.gitbook/assets/image (52).png differ diff --git a/.gitbook/assets/image (53).png b/.gitbook/assets/image (53).png new file mode 100644 index 0000000..96f0b61 Binary files /dev/null and b/.gitbook/assets/image (53).png differ diff --git a/.gitbook/assets/image (54).png b/.gitbook/assets/image (54).png new file mode 100644 index 0000000..fd9cf1c Binary files /dev/null and b/.gitbook/assets/image (54).png differ diff --git a/SUMMARY.md b/SUMMARY.md index 1fdb439..dcca57c 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -66,7 +66,9 @@ * [Recovery Phrase](data-and-security/what-is-a-recovery-phrase.md) * [Privacy & Encryption](data-and-security/how-we-keep-your-data-safe.md) * [Storage & Deletion](data-and-security/data-storage-and-deletion/README.md) -* [Networks & Backup](data-and-security/data-storage-and-deletion/self-hosting.md) +* [Networks & Backup](data-and-security/self-hosting/README.md) + * [Local-only](data-and-security/self-hosting/local-only.md) + * [Self-hosted](data-and-security/self-hosting/self-hosted.md) * [Data Erasure](data-and-security/delete-or-reset-your-account.md) * [Analytics & Tracking](data-and-security/analytics-and-tracking.md) diff --git a/data-and-security/data-storage-and-deletion/self-hosting.md b/data-and-security/data-storage-and-deletion/self-hosting.md deleted file mode 100644 index b6fc3cb..0000000 --- a/data-and-security/data-storage-and-deletion/self-hosting.md +++ /dev/null @@ -1,44 +0,0 @@ -# Networks & Backup - -### Anytype Network - -Every Anytype user has access to a remote backup node provided by Anytype. Its capacity is currently limited to 1 GB. Objects and other content have no impact on this limit; only files are limited. If you go over the limit, a warning will appear, and you'll be able to ask for more storage. - -Our backup nodes are located in Switzerland. - -### **Self-hosted Network** - -To back up your spaces and data to a self-hosted network, you need to have a network configuration. If you don’t run your own network yet, see this [how-to guide](https://tech.anytype.io/how-to/self-hosting). - -Our contributors are already working on creating a Docker image to simplify the setup of self-hosted infrastructure. You can join by following this [discussion](https://github.com/orgs/anyproto/discussions/17) on our GitHub page. - -### Local-only Mode - -If you don't want to use any backup solutions at all, you can use our local-only mode. This will disable the backup node completely, and you will only be able to sync between your devices if they are connected to the same local network. Regularly exporting your spaces is recommended if you decide to use this mode since your data is not backed up anywhere. - -### Switching Between Networks - -We strongly recommend using dedicated identities for each network (local-only mode being the exception). If you are switching from a different network, export all your spaces, and import them into a new identity after switching the network mode. - -Please note that all your devices should be manually switched to the same network. - -#### Desktop - -1. Log out from your current identity. -2. On the onboarding screen, click a gear icon in the top right corner. -3. In the “Network” field pick the network mode you want to use. -4. If you picked the “Self-hosted” mode, upload your self-hosted network configuration (\*.yml file) to the corresponding field. -5. Click the “Save” button. -6. Create a new identity or log in with the existing one. - -
- -#### iOS & Android - -1. Log out from your current identity. -2. On the onboarding screen, click a gear icon in the top right corner. -3. Click on the network mode you want to use. -4. If you can't find your network in the list, you can add one by clicking the “Add self-hosted network” button, and choosing your self-hosted network configuration (\*.yml file). -5. Create a new identity or log in with the existing one. - -
diff --git a/data-and-security/self-hosting/README.md b/data-and-security/self-hosting/README.md new file mode 100644 index 0000000..dfd2083 --- /dev/null +++ b/data-and-security/self-hosting/README.md @@ -0,0 +1,34 @@ +# Networks & Backup + +### Anytype Network + +By default, everyone joins the Anytype network when they create a new account. They can later switch to either to [local-only.md](local-only.md "mention") or [self-hosted.md](self-hosted.md "mention") if they wish. + +Every Anytype user has access to a remote backup node provided by Anytype. Its capacity is currently limited to 1 GB. Objects and other content have no impact on this limit; only files are limited. If you go over the limit, a warning will appear, and you'll be able to ask for more storage. + +Our backup nodes are located in Switzerland, and we use AWS (Amazon Web Services). + +### How to switch back to Anytype network + +We strongly recommend using dedicated identities for each network. If you are switching from a Self-hosted network, export all your spaces, and import them into a new identity after switching the network mode. + +Please note that all your devices should be manually switched to Anytype Network mode. + +#### Desktop + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. In the “Network” field choose the “Anytype” option. +4. Click the “Save” button. +5. Create a new identity or log in with an existing one. + +
+ +#### Mobile + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. Click on “Anytype” in the “Networks” sub-menu. +4. Create a new identity or log in an existing one. + +
diff --git a/data-and-security/self-hosting/local-only.md b/data-and-security/self-hosting/local-only.md new file mode 100644 index 0000000..b992c01 --- /dev/null +++ b/data-and-security/self-hosting/local-only.md @@ -0,0 +1,24 @@ +# Local-only + +If you don't want to use any backup solutions at all, you can use our local-only mode. This will disable the backup node completely, and you will only be able to sync between your devices if they are connected to the same local network. Regularly exporting your spaces or backing up your work directory is recommended if you decide to use this mode since your data is not backed up anywhere else. + +### How to switch to local-only mode + +#### Desktop + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. In the “Network” field choose the “Local-only” option. +4. Click the “Save” button. +5. Create a new identity or log in with an existing one. + +
+ +#### Mobile + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. Click on “Local-only” in the “Networks” sub-menu. +4. Create a new identity or log in an existing one. + +
diff --git a/data-and-security/self-hosting/self-hosted.md b/data-and-security/self-hosting/self-hosted.md new file mode 100644 index 0000000..aaa6fd8 --- /dev/null +++ b/data-and-security/self-hosting/self-hosted.md @@ -0,0 +1,32 @@ +# Self-hosted + +To back up your spaces and data to a self-hosted network, you need to have a network configuration. If you don’t run your own network yet, see this [how-to guide](https://tech.anytype.io/how-to/self-hosting). + +Our contributors are already working on creating a Docker image to simplify the setup of self-hosted infrastructure. You can join by following the [discussion](https://github.com/orgs/anyproto/discussions/17) on our GitHub page. + +### How to switch to a self-hosted network + +We strongly recommend using dedicated identities for each network. If you already have an identity in Anytype Network and want to switch to a self-hosted network, export all your spaces, and import them into a new identity after switching the network mode. + +Please note that all your devices should be manually switched to the same self-hosted network. + +#### Desktop + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. In the “Network” field choose the “Self-hosted” option. +4. Upload your self-hosted network configuration (\*.yml file) to the corresponding field. +5. Click the “Save” button. +6. Create a new identity or log in with an existing one. + +
+ +#### Mobile + +1. Log out from your current identity. +2. On the onboarding screen, click a gear icon in the top right corner. +3. Click on “Self-hosted” in the “Networks” sub-menu. +4. Click on “Tap to provide your network configuration” to upload your self-hosted network configuration (\*.yml file). +5. Create a new identity or log in an existing one. + +