Mirror from bluesky-social/pds
add PDS migration notes (#315)
authored by
Alex Garnett
and committed by
GitHub
aaef1e53
ab53b246
+8
+8
README.md
+8
README.md
···
33
33
- [Updating your PDS](#updating-your-pds)
34
34
- [goat CLI](#goat-cli)
35
35
- [Environment Variables](#environment-variables)
36
+
- [Migrating your PDS](#migrating-your-pds)
36
37
- [License](#license)
37
38
38
39
<!-- tocstop -->
···
343
344
| `PDS_PRIVACY_POLICY_URL` | None |
344
345
| `PDS_RATE_LIMITS_ENABLED` | `true` |
345
346
347
+
### Migrating your PDS
348
+
349
+
Once you've deployed a PDS, it will automatically begin broadcasting events to Relay servers.
350
+
351
+
This means that if you wipe and reinstall your PDS on the same hostname, or move it to a new hostname without performing the appropriate cutover steps, the PDS and Relay can go out of sync.
352
+
353
+
To avoid this, you should always [migrate accounts individually](https://atproto.com/guides/account-migration) from one PDS to another when updating your PDS host configuration.
346
354
347
355
## License
348
356