anyproto/any-sync-dockercompose
1
0
Fork 0
mirror of https://github.com/anyproto/any-sync-dockercompose.git synced 2025-06-08 14:07:02 +09:00
Code Activity

UPGRADE.md: small fix

Browse source
This commit is contained in:
Grigory Efimov 2024-04-05 11:31:59 -03:00
parent 7ab27baaed
commit e2e673d8db
No known key found for this signature in database
GPG key ID: 0A88C34DFA7FD939
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
UPGRADE.md
View file

@ -24,7 +24,7 @@ in some cases it may be necessary to run ```make upgrade```
1. Check logs for any errors. ```docker-compose logs -f``` 1. Check logs for any errors. ```docker-compose logs -f```
2. Verify that all critical functionalities are working as expected. 2. Verify that all critical functionalities are working as expected.
## Upgrading from v1.x.x to 2.x.x ## Upgrading from v1.x.x to v2.x.x
Starting with version 2.0.1, we have switched from s3-emulator to MinIO for storing data uploaded via the any-sync-filenode daemon. Starting with version 2.0.1, we have switched from s3-emulator to MinIO for storing data uploaded via the any-sync-filenode daemon.
To preserve your data, you will need to manually migrate it from s3-emulator to MinIO. To preserve your data, you will need to manually migrate it from s3-emulator to MinIO.