A desktop WordPress site migration and synchronisation tool — a modern replacement for the wordmove CLI.
SiteSync provides a Filament-powered admin UI for managing multiple WordPress sites and syncing their databases and files between environments (local ↔ staging ↔ production). It handles SSH connectivity, encrypted credential storage, real-time sync logging, and site discovery from existing WordPress installs.
Built with Laravel 12, Filament 5, and NativePHP — runs as a web app or desktop app.
- Bidirectional sync — push or pull between any two environments
- Granular scope control — sync database, themes, plugins, mu-plugins, uploads, WordPress core, or custom paths independently
- Database sync — dump, import, and automatic URL/path search-replace (via WP-CLI or mysqldump)
- SSH key management — store keys as file paths or inline content; encrypted at rest
- Custom commands & hooks — execute one-off SSH commands or configure per-environment pre/post sync hooks (useful for WP-CLI tasks, find-replace, etc.)
- Automatic backups — pre-sync SQL backups before any database is overwritten
- Site discovery — auto-detect WordPress installs from a local path; parses
wp-config.phpandmovefile.yml - Movefile import — import site configs directly from existing movefile YAML
- Sync history — full log of every sync with command output, status, and duration
- Live terminal — real-time sync output streamed to the dashboard
- CLI commands — run push/pull syncs from the terminal without the UI
- Desktop app — ships as a NativePHP desktop application
| Layer | Package |
|---|---|
| Framework | Laravel 12 |
| Admin UI | Filament 5 |
| Frontend | Livewire 4, Alpine.js, Tailwind CSS v4 |
| Desktop | NativePHP 2 |
| Queue / Cache / Sessions | SQLite (database driver) |
| Testing | Pest 4 |
| Process execution | symfony/process |
| YAML parsing | symfony/yaml |
- PHP 8.4+
- Node.js 20+
- Laravel Herd (or a compatible local server)
- WP-CLI on target servers (recommended) or
mysqldump rsyncandsshavailable in the system PATH
git clone https://github.com/your-org/sitesync.git
cd sitesync
composer run setupThe setup script runs: composer install, copies .env.example → .env, generates the app key, runs migrations, and builds frontend assets.
composer install
cp .env.example .env
php artisan key:generate
php artisan migrate --force
npm install
npm run build# Start Laravel server, queue worker, log viewer, and Vite concurrently
composer run dev
# Or for the NativePHP desktop app
composer run native:devThe app will be available at https://sitesync.test via Laravel Herd.
Parses wp-config.php (and movefile.yml if present) to create site and environment records automatically.
php artisan sitesync:discover {path} [--name=] [--adapter=wpcli]php artisan sitesync:push {site} [--from=local] [--to=] [--db] [--themes] [--plugins] [--mu-plugins] [--uploads] [--core] [--files] [--all] [--path=*]php artisan sitesync:pull {site} [--from=] [--to=local] [--db] [--themes] [--plugins] [--mu-plugins] [--uploads] [--core] [--files] [--all] [--path=*]{site} accepts either the site ID or name. --files is shorthand for --themes --plugins --uploads. --all syncs everything.
sites
└── environments (local, staging, production, …)
└── sync_logs (push/pull history with output)
ssh_keys (reusable across environments)
Sensitive fields (db_password, ssh_password, SSH key content) are encrypted at rest using Laravel's encrypted cast.
- Local ↔ remote sync is supported in both directions.
- Remote-to-remote sync is not supported; use a local environment as an intermediary.
- Database sync steps: backup destination → dump source → import → URL search-replace → path search-replace (if paths differ).
- File sync uses
rsyncover SSH with configurable exclusions. Default exclusions include.git/,node_modules/,wp-config.php. - SSH string keys are written to a temporary file (chmod 600) and cleaned up on process exit.
composer run test
# or
php artisan test --compactWhether it’s writing docs, squashing bugs, or building new features, your contribution matters! ❤️
We welcome PRs, issues, ideas, and suggestions!
Here’s how you can join the party:
- Follow our coding style and best practices.
- Be respectful, helpful, and open-minded.
- Respect the CC BY-NC-SA license.
- Fork the repository
- Create a feature branch
- Add tests for new functionality
- Submit a pull request
SiteSync is licensed under CC BY-NC-SA 4.0:
- BY: Give credit where credit’s due.
- NC: No commercial use.
- SA: Share alike if you remix.
For full license details, see LICENSE.