You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Currently Cosmos CMS will synchronize file systems in real-time between two different accounts. For example, between S3 and Azure blob storage.
However, should a cloud provider go down, or when a new storage account is added, there is no automatic synchronization recovery. Synchronization must be done by hand.
Idea is to create a background service that can be triggered, or run as a "task," that will keep blob storage accounts synchronized.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently Cosmos CMS will synchronize file systems in real-time between two different accounts. For example, between S3 and Azure blob storage.
However, should a cloud provider go down, or when a new storage account is added, there is no automatic synchronization recovery. Synchronization must be done by hand.
Idea is to create a background service that can be triggered, or run as a "task," that will keep blob storage accounts synchronized.
Beta Was this translation helpful? Give feedback.
All reactions