Download the PHP package pushinbr/pam-native-sync without Composer

On this page you can find all versions of the php package pushinbr/pam-native-sync. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of pushinbr/pam-native-sync

Informations about the package pam-native-sync

# PAM Native Sync **Offline-first writes with explicit conflicts and resumable cursors.** Coordinate local outboxes, incremental pulls, retries, and deterministic conflict resolution without prescribing an application vertical. [![Latest version](https://img.shields.io/packagist/v/pushinbr/pam-native-sync?style=flat-square&label=stable)](https://packagist.org/packages/pushinbr/pam-native-sync) [![CI](https://img.shields.io/github/actions/workflow/status/push-in/pam-native-sync/ci.yml?branch=main&style=flat-square&label=CI)](https://github.com/push-in/pam-native-sync/actions) ![PHP](https://img.shields.io/badge/PHP-8.5-777BB4?style=flat-square&logo=php&logoColor=white) ![Android](https://img.shields.io/badge/Android-API%2026%2B-3DDC84?style=flat-square&logo=android&logoColor=white) ![iOS](https://img.shields.io/badge/iOS-15%2B-000000?style=flat-square&logo=apple&logoColor=white) **[Documentation](https://push-in.github.io/pam-docs/native/overview/) · [Quick start](#quick-start) · [What you can build](#what-you-can-build) · [PAM ecosystem](https://push-in.github.io/pam-docs/ecosystem/) · [Issues](https://github.com/push-in/pam-native-sync/issues)**

Why PAM Native Sync

Coordinate local outboxes, incremental pulls, retries, and deterministic conflict resolution without prescribing an application vertical. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
Best for A focused capability you can add to any PAM Native application
Native path Durable outbox · Cursor protocol
Application model Composer package + generated native integration
Design rule Independent module; no feed, vertical, or application template bundled

What you can build

The client is backend-agnostic. Its HttpSyncTransport speaks the documented JSON protocol and does not install or reference Laravel, PAM HTTP, or any server package:

Quick start

Already have a PAM Native project? Add only this capability:

New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.

An offline-first synchronization engine, not a database wrapper. It adds an idempotent outbox, ordered batches, incremental cursors, tombstones, retry budgets and deterministic conflict policies above PAM Native SQLite and any transport implementation.

See it in action

SyncTransport is provider-neutral. The built-in HTTP adapter works with Laravel, PAM HTTP, or any other compatible server without adding a backend package to the app. SQLite writes are prepared and remote changes plus cursor advancement are committed in one native transaction. Server versions are monotonic and stale pulls cannot overwrite newer replicas.

Local-first CRDTs

For collaboration that must converge before a server answers, the package also ships backend-free primitives: HybridLogicalClock, LogicalTimestamp, and LastWriteWinsMap. Clocks remain monotonic when wall clocks move backwards; map snapshots retain tombstones and merge deterministically across replicas.

CRDTs do not require pam-native-sync-laravel, PAM HTTP, or a specific cloud. Persistence and transport remain explicit application choices.

Platform support: Android API 26+, iOS 15+, PAM Native 0.8.x.

All versions of pam-native-sync with dependencies

PHP Build Version
Package Version
Requires php Version ^8.5
pushinbr/pam-native Version ^0.8 || ^0.9 || ^0.10 || ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package pushinbr/pam-native-sync contains the following files

Loading the files please wait ...