Page:
Template Repository Mirror
Pages
Archive Layout
Backup and Recovery
Baseline TrinityCore 3.3.5 001
Bug Tracker
Client Preservation
Compatibility Matrix
Contributing
Ecosystem Map
Findings Log
Governance and Safety
Home
Mirror Inventory
Preservation Metadata
Preservation Status
Repository Mirroring
Reproducible Baselines
Reverse Engineering Workflow
Runbook Clean Installation
Runbook Client Working Copy
Runbook Database Backup and Restore
Runbook Forgejo Recovery
Runbook Incident Recovery
Runbook Upgrade and Rollback
Runbooks
Server Astral Realm TW 012
Server Aura Kingdom
Server Catalog
Server FFXI LandSandBoat
Server FFXIV Project Meteor
Server FFXIV Sapphire
Server Grand Fantasia
Server WoW TrinityCore 3.3.5
Server WoW TrinityCore Master
Server X Legend Legacy
Template Bug
Template Client Snapshot
Template Finding
Template Repository Mirror
Template Server Profile
Template Tool
Templates
Tool AK Tools v1.0
Toolbox
Vision and Scope
No results
1
Template Repository Mirror
official-markus-maurer edited this page 2026-07-16 10:19:18 +02:00
Template — Repository Mirror
<host>/<owner>/<repository>
| Field | Value |
|---|---|
| Mirror ID | <host>/<owner>/<repository> |
| Canonical URL | <URL> |
| Historical URLs | <URLs or none> |
| Internal mirror | <Forgejo URL or restricted ID> |
| Acquired | <ISO 8601> |
| Last fetched | <ISO 8601> |
| Default branch | <name> |
| HEAD commit | <full object ID> |
| Object format | SHA-1 / SHA-256 |
| Git LFS | yes / no / unknown; verification date |
| Submodules | checked / none / unresolved; manifest link |
| License | <SPDX or NOASSERTION> |
| Access class | public / restricted / private |
| Backup locations | <opaque location IDs> |
| Restore tested | <date and evidence> |
Ref inventory
Link the sorted show-ref manifest and its checksum. Note force-pushes, deleted upstream refs, or refs intentionally excluded from a public mirror.
Related material
Issues, releases, wiki, docs, package registry, LFS, submodules, build dependencies, or external downloads that require separate preservation.
Update procedure
Exact safe update commands, cadence, logging, snapshot-before-prune policy, and expected authentication method without storing credentials.
Recovery procedure
Bundle/filesystem backup location ID, verification commands, checkout revision, LFS/submodule materialization, and last successful build/restore evidence.
Known gaps
<missing refs, LFS objects, submodule commit, license, or restore test>
Private Server Preservation
- Home
- Preservation Status
- Compatibility Matrix
- Ecosystem Map
- Vision and Scope
- Server Catalog
- Client Preservation
- Archive Layout
- Repository Mirroring
- Mirror Inventory
- Preservation Metadata
- Reverse Engineering
- Findings Log
- Bug Tracker
- Toolbox
- Reproducible Baselines
- Operational Runbooks
- Backup and Recovery
- Governance and Safety
- Contributing
- Templates
PrivateServer-RS preservation wiki · Originals remain immutable · Every artifact must be attributable and verifiable