- What is apptank/horusync used for in a Laravel application?
- apptank/horusync is a Laravel/PHP package that offers synchronization utilities to help keep application data consistent across systems. The technical evaluation positions it around bidirectional sync between offline-capable mobile clients and a Laravel backend. That implies change tracking, delta payloads, HTTP endpoints, and a client contract, but the provided material does not include a README excerpt or exact API details.
- How do I install apptank/horusync in Laravel?
- The evaluation describes installation as conventional for a Laravel package: Composer, a service provider, published config and migrations, and registered routes. It does not provide exact Composer commands or publish tags. Verify the vendor instructions before running migrations against a production database.
- Does apptank/horusync support offline mobile sync with Laravel?
- The package is described as targeting bidirectional synchronization between offline-capable mobile clients and a Laravel backend. The evaluation says this implies an opinionated sync engine with change tracking, delta payloads, and a conflict-resolution policy plus a client contract. It does not confirm which mobile platforms or SDKs are supported.
- Which Laravel and PHP versions does apptank/horusync support?
- The provided material does not specify supported Laravel or PHP version bands. The technical evaluation explicitly recommends confirming the Laravel version band, PHP minimum, supported databases, queue and scheduler requirements, and whether a CI matrix exists. Treat version compatibility as an open question before adoption.
- Is apptank/horusync free for commercial SaaS use?
- The package is reported as AGPL-3.0 licensed, which the evaluation calls the single largest blocker. Offering the resulting service over a network can trigger source-disclosure obligations for the combined work. For commercial SaaS or on-prem products, plan for legal sign-off, complete source release, or a negotiated commercial license from Apptank SAS.
- How does apptank/horusync handle conflict resolution?
- The provided material does not identify the implemented conflict-resolution policy. The evaluation lists last-write-wins, server-authoritative, vector clocks, and CRDTs as questions to confirm, and asks whether the policy is configurable per entity. Do not assume a specific policy until the vendor documents it.
- Does apptank/horusync secure sync endpoints and support multi-tenant scoping?
- The evaluation warns that sync endpoints are a common source of over-broad read and write surfaces. It says authentication, tenancy scoping, and payload authorization must be verified against your Sanctum or Passport setup and policies. The provided material does not confirm a built-in authorization model or per-tenant scoping.
- Are there tests and community adoption for apptank/horusync?
- The evaluation reports zero stars, zero dependents, and no external adopters, so there is no community backstop or third-party bug reporting. It also asks whether published tests exist and what coverage applies to conflict and retry paths. Treat the package as single-vendor software and request testing evidence before relying on it.
- Why does apptank/horusync have a 2026 release date?
- The last release is dated 2026-10-16, which is a future date relative to normal release cadence. The evaluation says this could be a misconfigured tag, a timezone or formatting artifact, or a placeholder. It undermines confidence in release hygiene and should be resolved before any dependency decision.
- What should I check before choosing apptank/horusync over an alternative?
- The provided material does not name specific alternatives. It says architectural fit is plausible for a Laravel monolith with a first-party mobile app, but degrades for SPA-only, microservices, third-party mobile clients, and multi-tenant SaaS with strict isolation. Before choosing it, confirm licensing, protocol documentation, client SDK status, authorization, test coverage, supported databases, and release history.