- How do I install aerni/sync in a Laravel app?
- Install it with Composer as aerni/sync, then publish its configuration file and define your remote and local environment targets. You will typically provide SSH connection details, remote paths, local paths, and any exclusions before running the Artisan sync commands. Validate PHP and Laravel version constraints and confirm non-interactive SSH works before piloting it in a sandbox.
- Which Laravel and PHP versions does aerni/sync support?
- The provided context does not list exact Laravel and PHP version constraints, so check the package composer.json and release notes before adopting it. Test the package with config caching enabled in a sandbox that matches your target Laravel version. Pin the version you validate and recheck constraints when upgrading Laravel or PHP.
- How do I configure SSH connections and remote paths for aerni/sync?
- Configuration is expected to cover SSH host, user, authentication method, local and remote paths, and exclusions. Keep credentials in environment variables or a secret manager rather than committed config files. Confirm host-key verification and non-interactive SSH behavior before using it against shared or staging environments.
- Can I exclude files or folders from a Laravel sync?
- The package blurb specifically mentions configurable exclusions, so you can likely filter paths such as vendor, node_modules, .env files, and generated storage content. Treat exclusions as a safety control and prefer an explicit allowlist for non-source files. Test the resulting file set with a dry run or checksum manifest before transferring.
- Does aerni/sync support dry runs or previews before transferring files?
- The technical assessment requires dry-run and backup controls, but the exact Artisan flags are not confirmed in the provided context. Check the command help output and review the source before relying on any preview mode. If dry run is missing or unclear, wrap the package in a script that captures a backup and checksum manifest first.
- Is aerni/sync safe to use against production environments?
- It should not be treated as a production runtime dependency or a deployment replacement. File-moving commands carry destructive potential, including unintended deletion, overwriting newer files, wrong-environment targeting, and partial transfers. Restrict it to allowlisted, non-source files in controlled environments, add locks and logging, and technically block production targets unless a reviewed runbook and backups exist.
- Can aerni/sync sync databases as well as files?
- The package marketing mentions syncing databases, but the technical evaluation positions aerni/sync primarily as a file and folder transfer utility and warns that databases are a poor fit. For schema changes use migrations, and for data use native database dump and import tooling with backups. If you need database syncing, verify the package source and test it heavily before trusting it with stateful data.
- What are alternatives to aerni/sync for Laravel file syncing?
- Common alternatives are native rsync or scp scripts, Laravel filesystem abstraction or S3-compatible storage for runtime assets, Git and CI for code, and migrations for schema. aerni/sync is best viewed as an Artisan convenience wrapper rather than a replacement for those tools. Choose based on auditability, backup behavior, allowlisting, and whether the workflow needs production-grade guarantees.
- How do I test aerni/sync in CI or on Windows?
- Verify that the CI image or Windows host has the required SSH and rsync tooling, compatible path separators, case sensitivity behavior, and file permissions. Run a sandbox proof of concept with config caching enabled and non-interactive SSH host verification. Also test partial failures and exit codes so your pipeline can fail safely instead of leaving an incomplete sync.
- Is aerni/sync actively maintained and production-ready?
- The package has thin adoption, with 67 stars and zero dependents, which suggests limited community validation and a likely single-maintainer bus factor. A recent release is positive for freshness but is not proof of maturity or production readiness. Pin the version, review the source where production-adjacent, and treat it as a guarded developer utility with backups, logging, and rollback controls.