Usage
Create watcherConfig.txt that contains entries like:
[project_name]
local_dir = /your/local/path
remote_dir = /your/remote/path
remote_addr = username@server
remote_port = {port}
[project_name]
local_dir = /your/local/path
remote_dir = /app
remote_addr = {username@server|server}
languages = {c++|all}
ignore_filetypes = {.so*|.so*,.cpp...}
file_delete = {True|False}
Language, remote_port, ignore_filetypes are optional
ignore_filetypes is useful if you have embedded c++ code in your project and the machine you're syncing to isn't the same type of machine as the one you're developing on.
The all language will sync the entired directory over. By default the language is python
file_delete will default to True, but if set to False will not delete files on remote if they don't exist on local. This is useful for building env-specific stuff that you don't want overwritten by a different env (or if you don't build on local because you can't or something).
server can be an alias set in your ~/.ssh/config
cysnc uses rsync every time a change to a local_dir is made.
Installation
pip install csync
TODO
- Have codeSync create the config files for you
- Extend makefile commands so that
makeisn't the only one - Enable force-sync
- Sync both ways
Metadata
Release files for csync 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| csync-0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for csync-0.1-py2.py3-none-any.whl |
Release files / csync-0.1-py2.py3-none-any.whl
| Download URL | csync-0.1-py2.py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5f40ba6473ad035939f806192c6008b75772236d7cac6c92f57d953e7c25106a
|
|
BLAKE2b-256 checksum How to use checksums |
ce16bda076d04a8de7159446066e62f77f47a8a98017b3104ef5dbd2e37cc699
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.2
|
Security for csync 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.