Sync

Peer-to-peer data sync between PhoenixKit instances, such as dev and prod or two separate websites. A sender connection lets a remote site pull chosen tables, with tokens, table allow/deny lists, limits, IP whitelists and expiry; one-time transfers use 8-character codes. Every transfer is recorded with history and an audit trail.

Use it when

• You want to copy production data into a dev or staging site
• Two of your sites need to share tables under controlled access

What it gives you

• Permanent token-based connections with automatic cross-site registration
• Incoming policies: auto accept, require approval, require password, deny all
• Ephemeral code-based one-time transfers
• Allowed/excluded tables, download and record limits, IP whitelist, time windows
• Conflict strategies skip, overwrite, merge, append; Oban background import
• Transfer history and activity audit; admin under /admin/sync

Example

config :phoenix_kit_sync,
  allow_internal_urls: false,
  excluded_tables: ["my_app_api_clients"]

Nothing posted about Sync yet. Read its changelog or see all PhoenixKit news.