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
The current bridge service functionalities just upload or fetch only EXISTING nodes
which means if I remove a node from LOCAL service and then push to REMOTE service, this node won't be removed
at REMOTE. Because the fetch and push functionalities are based on new node creations and updations.
We need an independent command and service functionality to migrate all data to another service.
--- BASIC USAGE CASE ---
notya migrate
Remote selection prompt:
>
- FIREBASE
- OTHER-REMOTE-SERVICE
Then it'll remove all nodes from the selected remote service and upload local nodes.
The text was updated successfully, but these errors were encountered:
The current bridge service functionalities just upload or fetch only EXISTING nodes
which means if I remove a node from LOCAL service and then push to REMOTE service, this node won't be removed
at REMOTE. Because the
fetch
andpush
functionalities are based on new node creations and updations.We need an independent command and service functionality to migrate all data to another service.
--- BASIC USAGE CASE ---
Remote selection prompt:
Then it'll remove all nodes from the selected remote service and upload local nodes.
The text was updated successfully, but these errors were encountered: