Remote sync for Better state.

better-remote stores Better objects, metadata, and frontier state so multiple checkouts can exchange native source-control history.

Hosted Remote

Hosted Better remote sync is coming soon. Today, use the self-hosted better-remote service for remote coordination.

Run A Local Remote

Start the remote service with a local storage directory:

better-remote --bind 127.0.0.1:8787 --storage-root .better-remote

Configure a repository and sync Better state:

better remote init local --url http://127.0.0.1:8787
better sync push
better sync pull

Docker Compose

The release repository includes Compose files for three storage modes. Filesystem is docker compose up -d --build. Local-dev MinIO adds -f docker-compose.minio.yml. Real AWS S3 adds -f docker-compose.s3.yml with BETTER_REMOTE_S3_* set. Loopback without Compose still uses --storage-root.

docker compose up -d --build
docker compose -f docker-compose.yml -f docker-compose.minio.yml up -d --build
docker compose -f docker-compose.yml -f docker-compose.s3.yml up -d --build

See docker/README.md for authentication, the local-dev MinIO credentials, and S3 variables.

Remote Coordination Rule

If push reports that the remote frontier advanced, pull first and inspect Better status before continuing. Reconcile the work instead of overwriting remote state.