content-distribution-receiver — the target side of the distribution line.

content-distribution-receiver is the companion package to moselwal/content-distribution-source. It receives signed DAG snapshots from the source webhook, validates the Ed25519 signature, maps UUIDv7 references onto the local TYPO3 ID space and writes the records into the local schema — while preserving local per-language overrides. Coming soon — API and content will follow once the package is cleared for public release.

What it will do

Summarised from the source README, here is what the receiver side has to deliver:

Webhook endpoint accepts the source’s push ping, validates the bearer token, the Ed25519 signature over canonical JSON (RFC 8785) as well as nonce and timestamp drift (±300 s, nonce cache 600 s).
Pull client calls the source’s pull endpoint authenticated, downloads the DAG snapshot and sends an ack at the end.
UUIDv7 mapping — every record is referenced by origin_uuid; the receiver maps them onto its own ID space.
Preserve local per-language edits — if the receiver continued to edit a translation locally, that stays; only the default record is overwritten.
FAL binaries are pulled from the source via signed URLs, not inlined in the snapshot.

Blog

Archiv →

content-distribution-source, TYPO3 multi-site, TYPO3 content syndication, workspace distribution, Ed25519 signature

content-distribution-source

content-distribution-source — central TYPO3 source side for multi-site content distribution. Signed DAG snapshots from workspace publish, Ed25519 signature, push ping plus pull fetch.

Next step

Setting up a TYPO3 receiver early?

If you sit on the receiving side of a TYPO3-to-TYPO3 distribution and want early access to the receiver package, get in touch — I coordinate setup, UUIDv7 migration of the existing record base and validation of the signature chain between source and receiver.

Request early access →

Or email us directly: kontakt@moselwal.de

content-distribution-receiver — the target side of the distribution line.

What it will do

Availability: coming soon — public release in preparation

Blog

content-distribution-source