SYNC-CONTENT(1)

💅 SYNC-CONTENT(1) — the user-commands girlies know 💅

okay bestie, sit down, we're learning sync-content today and honestly? it's giving organized. it's a User Commands situation, the manual is called SYNC-CONTENT(1), and it does exactly one thing extremely well: synchronize directory, file, and symlink structure. no cap. ✨

---

🌸 NAME 🌸

sync-content</purl> — synchronize directory, file, and symlink structure 🦋

---

✨ SYNOPSIS ✨

sync-content [-h] from to

that's it. that's the whole vibe. two paths and a dream. 🎀

---

💖 DESCRIPTION 💖

so the sync-content command synchronizes the file, directory, and symbolic link structure from the source path from to the destination path to. literally just copying the shape of one place into another place. 💅

and here's the part where it gets smart: only entries that differ between the source and destination get updated. entries that are identical? skipped. left alone. not even looked at twice. this is to minimize unnecessary work, and honestly, respecting her time. main character energy fr fr. 👑

the operation is one-way: changes flow from from to to. no deletions or modifications are performed in the source. so your original is safe, untouched, unbothered, moisturized, in her lane, focused, flourishing. 🫶

---

🔥 OPTIONS 🔥

• -h — display a help message summarizing usage, arguments, and options, then exit. like a little "hey bestie here's the rundown" and then she's gone. 💨

---

🌈 FEATURES 🌈

⚡ Efficient synchronization

only changed or missing entries are copied, which reduces I/O and runtime. no wasted motion, no wasted cycles. she's efficient like that. 🍓

🏛️ Structure preservation

directories, regular files, and symbolic links are replicated exactly. not approximately. not "close enough". exactly. 💯

🛡️ Non-destructive

existing matching files in the destination are left untouched. she does not come for what's already correct. periodt. ✋

---

🎀 ARGUMENTS 🎀

• from — the source directory whose contents will be synchronized. your origin story. your blueprint. 🌱
• to — the target directory that will receive updated or missing entries. the glow-up destination. 💫

---

⭐ EXIT STATUS ⭐

• 0 — successful completion. she ate and left no crumbs. 🔥
• non-zero — an error occurred during synchronization. 😭 something went wrong bestie, check the vibes.

---

🧚 EXAMPLES 🧚

synchronize the contents of ./src into ./backup:

sync-content ./src ./backup

and that's it. that's the whole ritual. 🕯️✨

---

💜 NOTES 💜

sync-content is a lightweight JavaScript implementation inspired by rsync(1), providing a simplified one-way synchronization mechanism suitable for development workflows and tooling environments. she's the low-key cousin of a big famous tool and she's thriving. 🙈

it is used internally by tshy(1) a javascript enhanced builder to replicate directory structures and ensure consistent project layouts. so yes, she's the one behind the scenes keeping everything cute and consistent. iykyk. 👑

⚠️ important, bestie: the command does not remove files or directories that exist in the destination but not in the source. it only adds and updates. nothing gets deleted. ever. no surprises, no casualties. 💀✨

---

🔍 SEE ALSO 🔍

rsync(1), cp(1), find(1), tshy(1)

---

🫶 AUTHOR 🫶

Written by Bastien Roucariès from Isaac Z. Schlueter documentation. absolute icons, both of them. 💖

---

and that's the tea, bestie. this whole thing is sync-content, dated December 2025, living in the User Commands section, and she's out here doing one-way synchronization with zero drama and maximum structure preservation. go forth and sync. 🌸🦋💅