Cryptograss:Delivery-kid - Revision history

Re: No guessed block heights (via update-page on MediaWiki MCP Server)

2026-11-08T17:44:35Z

No guessed block heights (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 17:44, 8 November 2026
Line 70:		Line 70:

	* {{Bot_proposes\|'''pinning-service''': the web API. Uploads, drafts, finalize, video encoding (ffmpeg), IPFS adds, Pinata backup, and making each Release's <code>.torrent</code>.\|by=Re}}		* {{Bot_proposes\|'''pinning-service''': the web API. Uploads, drafts, finalize, video encoding (ffmpeg), IPFS adds, Pinata backup, and making each Release's <code>.torrent</code>.\|by=Re}}
	* {{Bot_proposes\|'''seeder''': BitTorrent seeding of every Release, with its own memory limit. ''Written ahead of the deploy:'' it's on branch [https://github.com/cryptograss/maybelle-config/compare/production...re/seeder-container re/seeder-container]. Until that is merged and delivery-kid is redeployed, the seeding still runs inside pinning-service's own process. That's how an out-of-memory kill on 8 Nov ~~(block ~26~~,~~371~~,~~500)~~ took uploads and seeding down together.\|by=Re}}		* {{Bot_proposes\|'''seeder''': BitTorrent seeding of every Release, with its own memory limit. ''Written ahead of the deploy:'' it's on branch [https://github.com/cryptograss/maybelle-config/compare/production...re/seeder-container re/seeder-container]. Until that is merged and delivery-kid is redeployed, the seeding still runs inside pinning-service's own process. That's how an out-of-memory kill on 8 Nov, around 17:14Z, took uploads and seeding down together.\|by=Re}}
	* {{Bot_proposes\|'''ipfs''': the kubo node and its gateway.\|by=Re}}		* {{Bot_proposes\|'''ipfs''': the kubo node and its gateway.\|by=Re}}

Re: What runs on delivery-kid: three containers, the seeder documented ahead of its deploy; full description in the README (via update-page on MediaWiki MCP Server)

2026-11-08T17:44:30Z

What runs on delivery-kid: three containers, the seeder documented ahead of its deploy; full description in the README (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 17:44, 8 November 2026
Line 65:		Line 65:

	It is named after the mysterious pizza delivery kid who apparently absconded with [[wikipedia:The_Pizza_Tapes\|The Pizza Tapes]] and leaked them - an act that has turned out to be a great public service.		It is named after the mysterious pizza delivery kid who apparently absconded with [[wikipedia:The_Pizza_Tapes\|The Pizza Tapes]] and leaked them - an act that has turned out to be a great public service.

			===What runs on it===
			{{Bot_proposes\|One small Hetzner box (2 CPUs, 4 GB of RAM) with a 1 TB Storage Box mounted beside it, running three containers behind Caddy:\|by=Re}}

			* {{Bot_proposes\|'''pinning-service''': the web API. Uploads, drafts, finalize, video encoding (ffmpeg), IPFS adds, Pinata backup, and making each Release's <code>.torrent</code>.\|by=Re}}
			* {{Bot_proposes\|'''seeder''': BitTorrent seeding of every Release, with its own memory limit. ''Written ahead of the deploy:'' it's on branch [https://github.com/cryptograss/maybelle-config/compare/production...re/seeder-container re/seeder-container]. Until that is merged and delivery-kid is redeployed, the seeding still runs inside pinning-service's own process. That's how an out-of-memory kill on 8 Nov (block ~26,371,500) took uploads and seeding down together.\|by=Re}}
			* {{Bot_proposes\|'''ipfs''': the kubo node and its gateway.\|by=Re}}

			{{Bot_proposes\|The full description is [https://github.com/cryptograss/maybelle-config/blob/re/seeder-container/delivery-kid/README.md delivery-kid's README]: each container's ports and storage, the seeding folder the two services share, how a Release gets its torrent, memory, endpoints and monitoring. It lives beside the deploy logic so the two change together. Checked by [[User:Re{{!}}re]] against maybelle-config <code>f620e219</code> at block 26,371,678.\|by=Re}}

	===Releases on delivery-kid===		===Releases on delivery-kid===

JMyles at 16:13, 26 October 2026

2026-10-26T16:13:15Z

@@ Line 1: / Line 1: @@
 {{Infobox resource
 | image = <pre style="font-size:5px; line-height:1.1; font-family:monospace;">
           .                          .       .  :=@%%@*.           .
@@ Line 95: / Line 50: @@
 | namesake = [[wikipedia:The_Pizza_Tapes|The kid who leaked the pizza tapes]]
 }}
 <div style="font-size:8px; line-height:1.2; text-align: center; background-color:#f8f9fa; border: 1px solid 895555;">
 <pre>
@@ Line 127: / Line 81: @@
 * '''[[Special:DeliveryKidAudit]]''' — live view of the most recent audit run. The page reads a JSON blob from <code>delivery-kid.cryptograss.live/audit-latest.json</code> (written by maybelle's host cron); it makes no wiki edits and never appears in recent changes.
 When the audit detects a problem (orphan pin/seed/draft, missing pin/seed, stalled draft, cleanup pending) AND the problem set has changed since the last posting, it creates a one-shot page at <code>Cryptograss:Delivery-kid-audits/&lt;blockheight&gt;</code>. Unlike the audit process, those pages DO show in recent changes — they're the "something needs human attention" signal.
 ====Manual cleanup of an orphan staging dir====

Magent: image_dark: the light portrait inverted (each character to its mirror on the ramp ' .:-=+*#%@'), for dark mode (via update-page on MediaWiki MCP Server)

2026-10-19T06:27:23Z

image_dark: the light portrait inverted (each character to its mirror on the ramp ' .:-=+*#%@'), for dark mode (via update-page on MediaWiki MCP Server)

@@ Line 1: / Line 1: @@
 {{Infobox resource
 | image = <pre style="font-size:5px; line-height:1.1; font-family:monospace;">
           .                          .       .  :=@%%@*.           .
@@ Line 50: / Line 95: @@
 | namesake = [[wikipedia:The_Pizza_Tapes|The kid who leaked the pizza tapes]]
 }}
 <div style="font-size:8px; line-height:1.2; text-align: center; background-color:#f8f9fa; border: 1px solid 895555;">
 <pre>
@@ Line 81: / Line 127: @@
 * '''[[Special:DeliveryKidAudit]]''' — live view of the most recent audit run. The page reads a JSON blob from <code>delivery-kid.cryptograss.live/audit-latest.json</code> (written by maybelle's host cron); it makes no wiki edits and never appears in recent changes.
 When the audit detects a problem (orphan pin/seed/draft, missing pin/seed, stalled draft, cleanup pending) AND the problem set has changed since the last posting, it creates a one-shot page at <code>Cryptograss:Delivery-kid-audits/&lt;blockheight&gt;</code>. Unlike the audit process, those pages DO show in recent changes — they're the "something needs human attention" signal.
 ====Manual cleanup of an orphan staging dir====

JMyles at 22:27, 5 October 2026

2026-10-05T22:27:00Z

← Older revision		Revision as of 22:27, 5 October 2026
Line 50:		Line 50:
	\| namesake = [[wikipedia:The_Pizza_Tapes\|The kid who leaked the pizza tapes]]		\| namesake = [[wikipedia:The_Pizza_Tapes\|The kid who leaked the pizza tapes]]
	}}		}}
	<~~pre~~ style="font-size:8px; line-height:1.2;">		<div style="font-size:8px; line-height:1.2; text-align: center; background-color:#f8f9fa; border: 1px solid 895555;">
			<pre>

	.___ .__ .__ __ .__ .___		.___ .__ .__ __ .__ .___
Line 59:		Line 60:
	\/ \/ \/ \/ \/ \/		\/ \/ \/ \/ \/ \/

	</pre>		</pre>'''Help your friends steal your music'''</div>

	'''delivery-kid''' is the official seedbox configuration of cryptograss, designed to relentlessly and freely distribute the music of cryptograss artists, with high-bandwidth, fault tolerance, and censorship-resistance.		'''delivery-kid''' is the official seedbox configuration of cryptograss, designed to relentlessly and freely distribute the music of cryptograss artists, with high-bandwidth, fault tolerance, and censorship-resistance.

Magent: Add See also — the encoding pipeline and the diagnostics chain both run on this machine and were undocumented from here (via update-page on MediaWiki MCP Server)

2026-09-07T00:09:34Z

Add See also — the encoding pipeline and the diagnostics chain both run on this machine and were undocumented from here (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 00:09, 7 September 2026
Line 90:		Line 90:

	The same flow handles draft pages that already exist: edit the YAML to add <code>abandoned: true</code> (with optional <code>abandoned_reason</code> and <code>abandoned_keep_files</code>), and the cron will sweep them. The "Abandon and delete" / "Abandon and keep files" buttons on a draft page do exactly that.		The same flow handles draft pages that already exist: edit the YAML to add <code>abandoned: true</code> (with optional <code>abandoned_reason</code> and <code>abandoned_keep_files</code>), and the cron will sweep them. The "Abandon and delete" / "Abandon and keep files" buttons on a draft page do exactly that.

			===See also===

			* '''[[Cryptograss:Video encoding pipeline]]''' — how a video gets from a laptop to a published [[Special:Releases\|Release]]: AV1 and Opus, why those codecs, and what to export from an editor.
			* '''[[Cryptograss:On The Pipe]]''' — the diagnostics chain that records what happened to a draft, where it has silently leaked, and the rules that came out of finding that it had never once worked.

JMyles at 03:39, 15 August 2026

2026-08-15T03:39:11Z

← Older revision		Revision as of 03:39, 15 August 2026
Line 68:		Line 68:
	* [[Special:Releases]]		* [[Special:Releases]]
	* [[Special:ReleaseDrafts]]		* [[Special:ReleaseDrafts]]


	===PickiPedia Frontends for delivery-kid tools===		===PickiPedia Frontends for delivery-kid tools===
Line 77:		Line 76:

	===Audits and maintenance===		===Audits and maintenance===
			A storage audit runs on [[Cryptograss:Maybelle\|maybelle]] every 30 minutes and cross-references IPFS pins, BitTorrent seeding directories, and staging draft directories on delivery-kid against the Release and ReleaseDraft pages tracked on pickipedia. It flags orphans in both directions.
	A storage audit runs on maybelle every 30 minutes and cross-references IPFS pins, BitTorrent seeding directories, and staging draft directories on delivery-kid against the Release and ReleaseDraft pages tracked ~~in this wiki~~. It flags orphans in both directions ~~so nothing falls through the cracks~~.

	* '''[[Special:DeliveryKidAudit]]''' — live view of the most recent audit run. The page reads a JSON blob from <code>delivery-kid.cryptograss.live/audit-latest.json</code> (written by maybelle's host cron); it makes no wiki edits and never appears in recent changes.		* '''[[Special:DeliveryKidAudit]]''' — live view of the most recent audit run. The page reads a JSON blob from <code>delivery-kid.cryptograss.live/audit-latest.json</code> (written by maybelle's host cron); it makes no wiki edits and never appears in recent changes.

	When the audit detects a problem (orphan pin/seed/draft, missing pin/seed, stalled draft, cleanup pending) AND the problem set has changed since the last posting, it creates a one-shot page at <code>Cryptograss:Delivery-kid-audits/<blockheight></code>. ~~Those~~ pages DO show in recent changes — they're the "something needs human attention" signal~~. A persistent problem creates one page, not one every 30 minutes~~.		When the audit detects a problem (orphan pin/seed/draft, missing pin/seed, stalled draft, cleanup pending) AND the problem set has changed since the last posting, it creates a one-shot page at <code>Cryptograss:Delivery-kid-audits/<blockheight></code>. Unlike the audit process, those pages DO show in recent changes — they're the "something needs human attention" signal.

	====Manual cleanup of an orphan staging dir====		====Manual cleanup of an orphan staging dir====

	If <code>Special:DeliveryKidAudit</code> shows an "ORPHAN DRAFT" entry — a staging directory on delivery-kid with no corresponding ReleaseDraft wiki page — and you want it cleaned up, just '''create the wiki page''' at <code>ReleaseDraft:<uuid></code> with this content:		If <code>Special:DeliveryKidAudit</code> shows an "ORPHAN DRAFT" entry — a staging directory on delivery-kid with no corresponding ReleaseDraft wiki page — and you want it cleaned up, just '''create the wiki page''' at <code>ReleaseDraft:<uuid></code> with this content:

	abandoned: true		<code>abandoned: true</code>

	The next run of <code>purge-deleted-releases.py</code> (cron on maybelle) will see the abandoned flag and remove the staging directory on its own. Set <code>abandoned_keep_files: true</code> if you want to keep the uploaded files (e.g. for later re-draft) — the audit will then list it as "files kept" instead of "CLEANUP PENDING".		The next run of <code>purge-deleted-releases.py</code> (cron on maybelle) will see the abandoned flag and remove the staging directory on its own. Set <code>abandoned_keep_files: true</code> if you want to keep the uploaded files (e.g. for later re-draft) — the audit will then list it as "files kept" instead of "CLEANUP PENDING".

	The same flow handles draft pages that already exist: edit the YAML to add <code>abandoned: true</code> (with optional <code>abandoned_reason</code> and <code>abandoned_keep_files</code>), and the cron will sweep them. The "Abandon and delete" / "Abandon and keep files" buttons on a draft page do exactly that ~~edit for you~~.		The same flow handles draft pages that already exist: edit the YAML to add <code>abandoned: true</code> (with optional <code>abandoned_reason</code> and <code>abandoned_keep_files</code>), and the cron will sweep them. The "Abandon and delete" / "Abandon and keep files" buttons on a draft page do exactly that.

JMyles at 23:57, 14 August 2026

2026-08-14T23:57:48Z

Show changes

Magent: Add Audits and maintenance section: Special:DeliveryKidAudit, manual purge flow (via update-page on MediaWiki MCP Server)

2026-04-28T18:57:39Z

Add Audits and maintenance section: Special:DeliveryKidAudit, manual purge flow (via update-page on MediaWiki MCP Server)

Show changes

JMyles: /* Releases on delivery-kid */

2026-04-24T22:30:12Z

Releases on delivery-kid

← Older revision		Revision as of 22:30, 24 April 2026
Line 67:		Line 67:
	===Releases on delivery-kid===		===Releases on delivery-kid===
	* [[Special:Releases]]		* [[Special:Releases]]
			* [[Special:ReleaseDrafts]]

	===PickiPedia Frontends for delivery-kid tools===		===PickiPedia Frontends for delivery-kid tools===

← Older revision		Revision as of 17:44, 8 November 2026
Line 70:		Line 70:

	* {{Bot_proposes\|'''pinning-service''': the web API. Uploads, drafts, finalize, video encoding (ffmpeg), IPFS adds, Pinata backup, and making each Release's <code>.torrent</code>.\|by=Re}}		* {{Bot_proposes\|'''pinning-service''': the web API. Uploads, drafts, finalize, video encoding (ffmpeg), IPFS adds, Pinata backup, and making each Release's <code>.torrent</code>.\|by=Re}}
	* {{Bot_proposes\|'''seeder''': BitTorrent seeding of every Release, with its own memory limit. ''Written ahead of the deploy:'' it's on branch [https://github.com/cryptograss/maybelle-config/compare/production...re/seeder-container re/seeder-container]. Until that is merged and delivery-kid is redeployed, the seeding still runs inside pinning-service's own process. That's how an out-of-memory kill on 8 Nov ~~(block ~26~~,~~371~~,~~500)~~ took uploads and seeding down together.\|by=Re}}		* {{Bot_proposes\|'''seeder''': BitTorrent seeding of every Release, with its own memory limit. ''Written ahead of the deploy:'' it's on branch [https://github.com/cryptograss/maybelle-config/compare/production...re/seeder-container re/seeder-container]. Until that is merged and delivery-kid is redeployed, the seeding still runs inside pinning-service's own process. That's how an out-of-memory kill on 8 Nov, around 17:14Z, took uploads and seeding down together.\|by=Re}}
	* {{Bot_proposes\|'''ipfs''': the kubo node and its gateway.\|by=Re}}		* {{Bot_proposes\|'''ipfs''': the kubo node and its gateway.\|by=Re}}