Runtime components and trust boundaries used by sync_mirrors.py for repository mirrors, releases, and streamed release assets
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Primary responsibility
• GitHub is the source of repository and release inventory
• The script creates missing Gitea pull mirrors and aligns mirror intervals
• Existing Gitea content is preserved rather than deleted
Trust boundary
• GitHub requests use a Bearer token when configured
• Gitea requests use token authentication
• Config values come from mirror.env and environment variables
Asset path
• Release assets are downloaded in chunks
• A temporary file avoids buffering large assets in memory
• Multipart upload sends the same stream to Gitea
Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export