Commands  ›   ›  Plantroom Preset Sync With Supabase

Plantroom Preset Sync With Supabase

writes to model Public API · not yet exposed

Coming soon

Before you run this

Supabase URL + API key + user bearer token resolvable.

After it runs

Local store + remote table reconciled for the given scope.

When to use this

Don't use this when

Acquiring the bearer — DocumentController OAuth handles that.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "plantroom_layout" Deterministic config preset

Decision flow

1) Validate resolvers.
2) Instantiate SyncPlantroomConfigWithAdelphos.
3) Await SyncAsync(scope).
4) Emit counts + errors.

What you'll see in the chat

on start
Syncing plantroom presets with Supabase…
thinking
Validating + migrating each local preset…
Pushing + pulling via REST…
on success
Pushed {pushed}, pulled {pulled}, skipped {skipped}.
on failure
Sync failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/plantroom_preset_sync_with_supabase
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

plantroompresetsyncwithsupabase · sync plantroom presets · supabase preset sync

Pillar