🪦 Is your feature request related to a problem? Please describe.
Because cross-device connectivity is a highlight of the KitX project, it is often necessary to synchronize code and jointly debug on multiple devices when developing KitX.
Previously, I synchronized code through a private git server, and needed to rebase git when officially submitting, which was not very convenient.
So we developed this tool and integrated it into the KitX SDK. You can execute the tool through the cheese scaffolding in the future.
🪧 Describe the solution you'd like
- Use
.sync-ignore file to identity which paths ignored and which extensions ignored.
- Use cheese to launch this tool, for example:
cheese -e sync-server to launch a server in current folder.
cheese -e sync-client to launch a client in current folder.
- Server will watch the folder for any file changes and provide files catalog in
/catalog endpoint.
- Client will request
/catalog endpoint every 1 sec for changes, and get new file content in /file/<path> endpoint.
🧾 Describe alternatives you've considered
No response
📎 Additional context
No response
🪦 Is your feature request related to a problem? Please describe.
Because cross-device connectivity is a highlight of the KitX project, it is often necessary to synchronize code and jointly debug on multiple devices when developing KitX.
Previously, I synchronized code through a private git server, and needed to rebase git when officially submitting, which was not very convenient.
So we developed this tool and integrated it into the KitX SDK. You can execute the tool through the cheese scaffolding in the future.
🪧 Describe the solution you'd like
.sync-ignorefile to identity which paths ignored and which extensions ignored.cheese -e sync-serverto launch a server in current folder.cheese -e sync-clientto launch a client in current folder./catalogendpoint./catalogendpoint every 1 sec for changes, and get new file content in/file/<path>endpoint.🧾 Describe alternatives you've considered
No response
📎 Additional context
No response