@antibusy/strapi-mercur-survey-plugin-sync
v0.1.0
Published
Framework-neutral signed survey binding synchronization for Strapi and Mercur
Downloads
260
Readme
Strapi–Mercur Survey Plugin Sync
@antibusy/strapi-mercur-survey-plugin-sync is the same optional server-side adapter installed in either host. It exchanges signed survey binding/change events. Survey definitions and responses remain in the provider; invitation ownership and seller permissions remain in each host.
const { createAdapter } = require('@antibusy/strapi-mercur-survey-plugin-sync');
const adapter = createAdapter({
localId: 'strapi-local',
peerId: 'mercur-local',
peerUrl: 'https://marketplace.example.com',
peerPath: '/survey-sync',
secret: process.env.SURVEY_SYNC_SECRET,
});On the other host, reverse localId and peerId and configure that peer's URL and inbound endpoint. Preserve existing IDs, secret and endpoint paths during migration. Enable allowHttp only for local development. Secrets must contain at least 32 characters.
Configure the Survey plugin's sync.package as @antibusy/strapi-mercur-survey-plugin-sync; all other sync options stay the same. createSyncAdapter is an alias of createAdapter. bindingEvent builds the existing allowlisted event payload.
The library owns protocol v1 signing, verification, peer identity validation, HTTP delivery and durable-acceptance validation. Hosts own durable outbox/inbox storage, retries, idempotency, loop prevention, business mapping and authorization. Installing this package does not enable sync automatically.
The previous directional packages remain compatibility wrappers. Their createAdapter signatures and diagnostic direction strings are preserved. No queue, binding, invitation or response migration is needed.
Local packaging
Run npm test, then npm pack. The package ships its own synchronization implementation in src/transport.cjs and protocol helpers in src/protocol.cjs. It uses only Node.js built-ins and has no runtime or development dependencies, generated runtime files, or build step. Both hosts consume the same artifact.
The legacy protocol fixture under tests/fixtures is frozen test data for checking interoperability with older peers; it is not shipped in the package.
