Runtime sequence of sync_mirrors.py: config, repository mirroring, release sync, streamed asset copy, orphan check, and exit status
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
Mirror ownership
• GitHub repositories drive the run; Gitea state is reconciled per repository
• Existing non-mirror repositories are warned about and left untouched
• Deleted or renamed upstream repositories are reported as orphaned mirrors
Release policy
• Release metadata is created or patched only when fields differ
• Draft handling waits until the mirrored tag exists in Gitea
• No Gitea-side release or asset is deleted by the script
Asset streaming
• GitHub assets download in chunks into a temporary file
• Multipart upload streams the temporary file to Gitea
• Existing same-name assets are preserved, with size mismatch warnings
Sequence 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