mirror of
https://github.com/anyproto/docs.git
synced 2025-06-08 05:47:05 +09:00
GITBOOK-255: Removed self-hosting page
This commit is contained in:
parent
322b0e8e82
commit
9f39c762d4
2 changed files with 0 additions and 37 deletions
|
@ -61,7 +61,6 @@
|
|||
## 🔍 Troubleshooting
|
||||
|
||||
* [Delete or Reset Your Account](troubleshooting/delete-or-reset-your-account.md)
|
||||
* [Self Host Your Backups](troubleshooting/self-host-your-backups.md)
|
||||
|
||||
## 🚵 MIgration
|
||||
|
||||
|
|
|
@ -1,36 +0,0 @@
|
|||
# Self Host Your Backups
|
||||
|
||||
All your data primarily syncs to the encrypted backup node in the current alpha. For alpha testers, the application is always connected to the backup node and cannot be disconnected.
|
||||
|
||||
#### Local backups
|
||||
|
||||
Anytype is offline-first, and our backup nodes are still in early testing (we can't guarantee data recovery in 100% of cases yet), it may be a good idea to do a regular backup of your Anytype folder to some safe place or with markdown Export. Here's how to find your Anytype folder:
|
||||
|
||||

|
||||
|
||||
#### Syncing. How does it work?
|
||||
|
||||
All objects are syncing separately. You can have 1 object in the actual state while another is downloading. Every object syncs with all historical changes being merged together. You can work being offline, with different devices different document states.
|
||||
|
||||
The app will transfer small chunks (those changes) of data that will build the document back in forth to devices and backup nodes. So when you open the document, not in its actual state. You just need to wait.
|
||||
|
||||
Later we will introduce more features bringing transparency into syncing.
|
||||
|
||||
#### P2P
|
||||
|
||||
We transfer objects directly between devices and backup nodes. That means that you can use the app on several devices in one network without connecting to the world wide web. Interconnections trying to establish with all machines being used with time intervals and if connected then checking changes, transfer data online. We can't broadcast every used device every second, so it can take some time to retrieve data from another device (restarting the app can help).
|
||||
|
||||
#### Status
|
||||
|
||||

|
||||
|
||||
* Status `Synced` is shown when: The app is backed on one node at least. If the app retrieved that no changes were made
|
||||
* Status `Syncing…` is shown when: For backup node: upload, download, pinning of files. For devices (direct interconnection): upload, download
|
||||
* Status `No connection` is shown when: Anytype node doesn't connect. You can send the data directly between devices.
|
||||
* Status `Not syncing` is shown when: The app fails to sync. It can be network problems or bugs.
|
||||
* Status `Preparing...` is shown when: Warming up and initializing synchronization.
|
||||
|
||||
Overall status (for an object):
|
||||
|
||||
* If the Object is not fully synced with some device or backup node and something is syncing (like a device), → then it is in `Syncing…` state
|
||||
|
Loading…
Add table
Add a link
Reference in a new issue