Repeatedly synchronize local workspace with a (slow) remote machine
Project description
LiveSync
Repeatedly synchronize local workspace with a (slow) remote machine. It is available as PyPI package and hosted on GitHub.
Use Case
VS Code Remote Development and similar tools are great as long as your remote machine is powerful enough. But if your target is a Raspberry Pi, Jetson Nano/Xavier/Orin, Beagle Board or similar, it feels like coding in jelly. Especially if you run powerful extensions like Pylance. LiveSync solves this by watching your code for changes and just copying the modifications to the slow remote machine. It works best if you have some kind of reload mechanism in place on the target (NiceGUI, FastAPI or Flask for example).
Usage
cd <my_project_folder>
livesync <username>@<host>
LiveSync uses rsync (SSH) to copy the files, so the <username>@<host> must be accessible via SSH (ideally by key, not password or passphrase, because it will be called over and over).
Press CTRL-C to abort the synchronization.
Notes
- We suggest you have some auto-reloading in place on the (slow) target machine, like NiceGUI.
- Only one user per target host should run LiveSync at a time. Therefore LiveSync provides a mutex mechanism.
- By default
.git/folders are not synchronized. - All files and directories from the
.gitignoreof any source directory are also excluded from synchronization. - You can create a
.syncignorefile in any source directory to skip additional files and directories from syncing. - If LiveSync finds a VSCode workspace file, it will synchronize each directory listed in the
folderssection.
Options
--on-change [command]command to be executed on remote host after any file change--source [SOURCE]source folder on local host instead of VSCode workspace file--mutex-interval [INTERVAL]interval for updating the mutex
Installation
python3 -m pip install livesync
Development
For development we suggest to use the following instructions instead of the normal pip installation:
git clone git@github.com:zauberzeug/livesync.git
cd livesync
python3 -m pip uninstall livesync # remove previous installed version
python3 -m pip install -e .
Now you can change the code and call the livesync command from your $PATH variable with the modified code.
Testing
We have build a small testing infrastructure with two docker containers. See tests/README.md for details.
Releases
Just create and push a new tag with the new version name (v0.2.1 for example). After a successful build a new release will be created. This should be edited to describe the changes in the release notes.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file LiveSync-0.2.2.tar.gz.
File metadata
- Download URL: LiveSync-0.2.2.tar.gz
- Upload date:
- Size: 6.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.11.4
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a4a65d1957b1bef526e79fd51ff6f360e7ee90892d7d28c6aacbc736717a4504
|
|
| MD5 |
7c5dac8c50f5a32f9265c195ce21fb41
|
|
| BLAKE2b-256 |
4a389cb13118c1db465bf1a9766f37cc705f9636edc8a04a041b8856aaadfb20
|
File details
Details for the file LiveSync-0.2.2-py3-none-any.whl.
File metadata
- Download URL: LiveSync-0.2.2-py3-none-any.whl
- Upload date:
- Size: 7.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.11.4
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
0f0baabe575b2f40f79adec8cfcff5c77ca440a69eb6bf915481961bda49b45a
|
|
| MD5 |
185aeb72babadcfcbcfd176d94ecf70d
|
|
| BLAKE2b-256 |
7ebc6fba227f25221d09f4a1f0519a5073a4bfd6911d31db49a45409c0f05807
|