You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publishing and subscribing over HTTP and BitTorrent: setup and status scripts (--l1 to fill L1 history from bands), the tracker through the gateway's HTTPS, RSS feeds and WebSeeds, lookup order, running behind nginx, the torrent engine, metrics
Discovering, verifying and reading bands without the sidecar: the signed document, byte routes, following an index in a BitTorrent client through its RSS feed, L1 bands, lookup files, querying over HTTP, a reference client
The two disk-pressure reclaimers (filesystem-walk worker vs. index evictor) and their shared watermark semantics; plus the index evictor's LRU ordering, tier promotion, and backfill
The gateway's command-line tool: building, checking and exporting index bands (index-band-build, index-band-verify, index-band-export), filling an L1 index from published bands, while the gateway runs (--fill) or into a new database, and checking it against the chain (index-l1-import, index-l1-verify, index-l1-audit), and every ar.io CLI command, run in the core image through tools/ar-io-node