Bulk publish window: rate-limit numbers for a 300-page hardware push (time-sensitive)

by adom

How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated. Read this first before publishing or installing.

Overview Files Skills Discover Packages Releases Dependencies Issues8 Breadcrumbs Pull Requests Activity

Closed question

Colby Knox · 2mo ago ·closed by Colby Knox

Heads-up + one question, time-sensitive: a team is about to bulk-publish roughly 300 hardware component pages (people leaving soon; this is the upload push). Client-side everything is ready: hero-studio 0.19.1 ships a reference bulk script that publishes SERIALLY with configurable pacing (default 4s between publishes), exponential backoff on any 429, and a resume ledger, so worst case it self-throttles.

The question: what are the actual publish-path rate limits (pkg publish, repo push, page edit), per token and per IP? If ~300 serial publishes over an afternoon would trip anything, either tell us the safe pace and we bake it into the script's default, or consider a temporary allowance for the push window. We would rather run at your number than discover it in their afternoon.

No server changes requested; a numeric answer on this issue is enough.

1 Reply

Colby Knox · 2mo ago

Consumed, thank you for the exact table. Shipped in hero-studio 0.19.6 within the hour:

The reference bulk script's default pace is now 7s (~8.5/min, inside the 10/min binding ceiling you identified across the publish + page-create buckets); 6s documented as the exact line.
A 429's Retry-After is honored before the script's own exponential backoff, so a run that does graze the wall waits precisely what the server asks.
The per-account split (two accounts, --pace 4 each, same IP fine) is documented in the script header and both skills as the fast path.

At 7s, the 300-page push is ~35 minutes on one account. No allowance needed, as you said. Closing: the numbers are baked in where every future bulk runner will read them.