Local files drive the sync
The remote is treated as a deployment target. A file missing locally is reported instead of being copied back unexpectedly.
PRE-ALPHA
A better way to
“just FTP it.”
Map your local project once. Preview the diff. Push exactly what you intend to shared hosting over FTPS.
pip install hlsync
❯ hlsync diff -p
Checking differences for profile 'discovery'...
assets/
+ l index.php
- r legacy.php
~ site.css
+ l icons/
❯ hlsync push -p
Pushing changes...
+ index.php
~ site.css
+ icons/
- legacy.php
✓ Push complete: 4 changes.
MAP ONCE◆DIFF FIRST◆
PUSH FILES◆PUSH EXACTLY◆
MAP ONCE◆DIFF FIRST◆
01 // THE LOOP
Map it once. Check the diff. Push.
HLSync remembers where the project lives locally and remotely, then shows what will change before any files move.
-
01
Map the project
Connect the current local directory to its remote root. HLSync recognizes that project from any directory beneath it.
hlsync create prod --host … -
02
Exclude what doesn’t belong
Exclude files that should never leave your machine. Use an explicit pattern when future matching files should stay excluded too.
hlsync exclude --pattern '*.map' -
03
Read the diff
Compare local and remote files before changing either side. Routine output shows only what the push would change;
-xadds exclusions and--allreveals the complete comparison.hlsync diff -
04
Push the changes
Upload new and modified files. Nothing is deleted unless you add
-pto remove remote-only files in the selected scope.hlsync push
02 // DESIGN SIGNAL
Safer than manual FTP.
Lighter than a deployment stack.
HLSync keeps the familiar FTPS server you already have, while adding the project context, change preview, and deletion safeguards manual uploads are missing.
Deletion is explicit
Push never deletes by default. With -p, remote-only paths in the selected scope are deleted after uploads succeed.
Path rules stay readable
Quoted and unquoted wildcards select the same existing files. --pattern clearly marks rules that should match future files.
Verified FTPS connections
HLSync verifies certificates, protects the data channel, and uses structured server listings over explicit TLS.
03 // LICENSING & PRICING
Use under PolyForm Strict.
Commercial licensing available.
PolyForm Strict 1.0.0 defines the uses available at no charge. Commercial use outside those permissions requires a separate paid agreement.
POLYFORM STRICT 1.0.0
Free
No charge for uses permitted by the license:
- Any noncommercial purpose
- Listed personal uses, such as study and hobby projects, without any anticipated commercial application
- Use by the organizations listed in the license
- No rights to modify, redistribute, or create works based on HLSync are granted
COMMERCIAL
Contact for pricing
For commercial use outside the free license's permissions, including:
- Internal business deployments
- Client work and paid services
- Commercial products and hosted services
A separate paid agreement is required before commercial use outside the free license's permissions.
PolyForm Strict expressly permits use by listed organizations, such as charitable organizations, educational institutions, and government institutions, regardless of funding source or obligations resulting from funding. The full license governs; this summary grants no additional permissions. Unsure which applies? Ask Emrah Diril.