N.I.N.A. Sync Plugin

PSF Guard Sync is a N.I.N.A. plugin that keeps a live Target Scheduler catalog in step with a PSF Guard server — pushing each capture as it lands and syncing plans and grades on demand, without the two-database CLI sync dance.

Preview / beta. The plugin is published on the beta channel (v0.1.0.0) and speaks the versioned /api/sync/v1 protocol. The PSF Guard server side of that protocol is still being built, so capture pushes return 404 until it ships — install it now to try the N.I.N.A. side and follow along.

Install it in N.I.N.A.

PSF Guard hosts its own N.I.N.A. plugin repository. Add it as a plugin source and PSF Guard Sync installs and updates like any other plugin:

  1. In N.I.N.A., open Options → Plugins.
  2. Add this repository URL:
    https://nina-plugins.psf-guard.com/
  3. Turn on “Include beta versions” — PSF Guard Sync ships on the beta channel.
  4. Find PSF Guard Sync in the Available list, install it, and restart N.I.N.A.
Requires Windows x64, N.I.N.A. 3.2.0.9001 or newer, and Target Scheduler schema 22+. The registry lives at nina-plugins.psf-guard.com.

How it works

The plugin subscribes to N.I.N.A.'s image-saved event. For each saved light frame it waits briefly for Target Scheduler to commit the matching acquiredimage row, builds a schema-preserving bundle of that capture plus its project, target, and plan dependencies, and drops it in a durable retry queue. Network work never blocks the image-save pipeline — if the server is unreachable, bundles wait and retry.

Configure it

Open Plugins → Installed → PSF Guard Sync and set:

  1. The PSF Guard server URL.
  2. The destination PSF Guard catalog ID.
  3. An API token (stored in Windows Credential Manager).
  4. The Target Scheduler database path (default %LOCALAPPDATA%\NINA\SchedulerPlugin\schedulerdb.sqlite).
  5. Your capture-push and preview-apply policy.

Use Test connection before enabling automatic pushes.

Sequencer instructions

The plugin also contributes instructions under PSF Guard Sync in the advanced sequencer:

Working from one machine, or syncing two SQLite files directly? The CLI psf-guard sync commands do the same job between database files, without the plugin.