PREVIEW ENVIRONMENT - This is not the production database. Changes will NOT be saved.
Cryptograss:Delivery-kid: Difference between revisions
No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| 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 74: | Line 75: | ||
* [[Special:DeliverBlueRailroad]] | * [[Special:DeliverBlueRailroad]] | ||
* [[Special:DeliverRecord]] | * [[Special:DeliverRecord]] | ||
===Audits and maintenance=== | |||
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. | |||
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. | |||
====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: | |||
abandoned: true | |||
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. | |||
Latest revision as of 23:57, 14 August 2026
| Delivery-kid | |
. . . :=@%%@*. .
. . . . . @= =#%+ =@%
. .%% @.. .+. -@. .
. . -@* . @. @@ @%=%.@ .. +@ .
. @.. %= @ @@. ::#@+* :@@%:..%. @ .
. . . . @=@ *@: # % %: @@%# :##@@*%*#:. .@ .
. . . -@@. @=- @%* @@@+#.@*.... @ .
@@ @: =+:@@@@@@@@.. @:..
. @# :%@=::*+::.@=.
. . *. =@@*@@* #@
. % . . - --...@@@ *@
. . .@....:::::::::::.:.:. . % -.+@@@@@%..-%
. . =*.+@@#-%%:-:::::::#@@+::.. ..@:%@%:::@: .
.. .@*:--::@@@@%:::::::::::@@@:. = %@@@@@@@* .
. . . . @--::::*@#-@@@@@#:::::::@@-@@:.::@. .
. . @=-:::::@:@%-:::::::::::::@@@@@@@::@#.. . .
. . . . @-::::::::::::::::::::::::=@@+@#@::+@* .
. @::::::::::::::::::::::::::*%*+%@::%%@. .
. . .@@@@@%::::::=%--*:::@=::::::::*+*:#:@:@* .. .
. . . .%@-:::%:::@::%%::-::@@-:::::::=@-@=@-@@. .
=#@ . =%+:@ . @-@::@@:::%:::::::::::::::::::%%:*@#@.
*%:@ ..*=:::%% . .. @:%@@+::::::::::::::::::::::::%-:#@- . .
. @::@.-*:::@* . . . *+::@::--::=:::::::-:::::::::::@:@@ .
@-@ :@::@=#:::@: .. . . . @::@-::::-*+:@@@@*+@--:::::::::@:%% .
@-%+:@-:@=*:::*.%::=*:. . ..%=::-@@-@@#@@@:@=::.@--::::::::*@-#@. .
#=:%:@:::@#:::@@::@=-::=@ . %=::@:=@::-@%-:::::::::::::@::%=#@@*@@+ .
%:=@#@:::@*::*:::** .+*-- . *%-@@%%*#:::::::::::::::::#=#*:@@#:::@@. . .
@:::@@**:::.@-::=@ **:@.. .@:-+%*:::::::::::::::::-@-@:%@@@::::*@@==+-
@-%:::::::::-:::@ **::@. @=:::#:::::::::::::::::%*:@#=@@@#:::*@-::
.. -@:::@*::@%*::::@+ @%:%*. +*-:@::::::::.@=:::::@:@-:@%::#%+:::#@@@. .
.@::::@*::::::::::@*::@. .@:@=::::::@#:::::+@=:+%=@=::: . . ==
@-::::=%:::::::::@+%:. .@::@%+%%-:::::=@=:@-.+@%.. .
%+::::::@:::::::::-@ . . .:@+::::::::@@@:@-#+:.*@= .
. @:::::::::-:::::-@. . .. . *@*:-=%@@=+@@:=@@@@= .
. @-:::::::::@:::%@@#%#. . . .=@@@@@@%:@.:@%.
:@:::::::::::#@%=*#@%.@@%*.:.=@@#@=:#@@@+@* . . .
. *@@-::::::::*: . . .%+::::-@@*=@: -:%:.: . . .
.@@@::::::::::. @%==%%@- .
%.#@:::::+@=%@ . . .
@= =. .#@: . .
@= . . . .
. . . . . . . . . .
| |
|---|---|
| the distributor | |
| Type | Server |
| Hostname | delivery-kid.cryptograss.live
|
| Services | IPFS, bit torrent, various open-source encoders and shit |
| Namesake | The kid who leaked the pizza tapes |
| Cryptograss Mythology | |
.___ .__ .__ __ .__ .___
__| _/____ | | |__|__ __ ___________ ___.__. | | _|__| __| _/
/ __ |/ __ \| | | \ \/ // __ \_ __ < | | ______ | |/ / |/ __ |
/ /_/ \ ___/| |_| |\ /\ ___/| | \/\___ | /_____/ | <| / /_/ |
\____ |\___ >____/__| \_/ \___ >__| / ____| |__|_ \__\____ |
\/ \/ \/ \/ \/ \/
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.
It is named after the mysterious pizza delivery kid who apparently absconded with The Pizza Tapes and leaked them - an act that has turned out to be a great public service.
Releases on delivery-kid
PickiPedia Frontends for delivery-kid tools
Audits and maintenance
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
delivery-kid.cryptograss.live/audit-latest.json(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 Cryptograss:Delivery-kid-audits/<blockheight>. 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.
Manual cleanup of an orphan staging dir
If Special:DeliveryKidAudit 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 ReleaseDraft:<uuid> with this content:
abandoned: true
The next run of purge-deleted-releases.py (cron on maybelle) will see the abandoned flag and remove the staging directory on its own. Set abandoned_keep_files: true 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 abandoned: true (with optional abandoned_reason and abandoned_keep_files), 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.
