Skip to main content

Cloud Sync & Versioning

Rephlo can keep your commands in two places at once: in the app on your computer, and in your account in the cloud. Cloud sync publishes a command to the online gallery so you can reuse it on another device, share it, or recover it later. Once a command is synced, Rephlo quietly keeps the local copy and the cloud copy in step.

This page explains how publishing works, what the sync-status labels mean, how Rephlo handles conflicts, and how background sync keeps things fresh.

Publishing a command to the cloud​

When you publish a command, Rephlo sends it to your account's online gallery and the server assigns it a permanent ID and a version number. You can optionally include a short changelog note describing what changed.

  • First publish creates a new gallery entry and stamps the local command with its online ID and version.
  • Later publishes of the same command push an update and bump the version number on the server.
  • Publishing requires you to be signed in. If your session has expired, Rephlo asks you to log in again and leaves the local copy untouched.

You don't have to track IDs or versions yourself — Rephlo records them on the command automatically after a successful publish.

Understanding sync status​

Every command tracks a sync status that tells Rephlo (and you) where it stands relative to the cloud copy.

StatusMeaning
NoneThe command has never been synced. It exists only on this computer.
SyncedThe local copy matches the latest version that the server confirmed. Nothing is pending.
DirtyThe command has local changes (or a failed publish) that still need to be pushed to the server.
ConflictBoth the local copy and the cloud copy changed independently. This needs attention before sync can continue.

After you edit a synced command, it becomes Dirty until the next successful publish returns it to Synced.

What happens when sync fails​

Rephlo is deliberately cautious so you never lose work:

  • Validation problems (for example, a field the server rejects) mark the command Dirty and show you the specific error, so you can fix it and try again.
  • Server or network errors also mark the command Dirty and Rephlo retries on the next sync cycle.
  • Sign-in problems never change your local sync state — you simply re-authenticate and retry.
  • If a command was deleted from your online gallery while the app still remembered its old ID, the next publish detects this and re-creates a fresh cloud copy automatically.

Bulk "Sync All"​

If several commands are Dirty, you can sync them all in one action instead of publishing each by hand. Rephlo optimizes this run so it stays fast and stays within the server's rate limits.

Conflict handling and background pull​

In the background, Rephlo periodically pulls your commands from the cloud and compares each one to your local copy by its online ID. The first pull runs shortly after the app starts, then it repeats on a regular cycle.

What happens on each pull depends on whether the cloud copy is newer and whether your local copy has unsaved changes:

Key points:

  • Cloud not newer → no change; Rephlo just refreshes online stats like install count and average rating.
  • Cloud newer, local clean → Rephlo updates the local copy and marks it Synced.
  • Cloud newer, local Dirty → Rephlo marks the command Conflict instead of overwriting your edits.
  • Background pull never creates brand-new local commands on its own — it only reconciles commands you already have.

If a command falls into the Conflict state, decide which version you want to keep, then re-publish to push your choice to the cloud (or let the cloud copy win by discarding your local edits).

Switching workspaces (organizations)​

If you belong to more than one workspace and switch between them, Rephlo does not overwrite a command that was synced into a different workspace. Instead, it publishes a fresh copy into your active workspace and leaves the other workspace's copy untouched. This keeps each workspace's gallery clean and avoids clobbering content you can no longer see.

Where to manage published commands​

The desktop app handles publishing and status; the web gallery is where your published commands live and where ratings and install counts come from.