[FEATURE]: Set up GitLab mirror as failover source of truth
Author: serengilCreated Apr 5, 2026Updated May 11, 2026
Labelsenhancement
Description
Description:
We have experienced multiple access issues with GitHub recently1, 2, which introduces a risk as it is currently our single source of truth. To mitigate this, we want to establish GitLab as a mirror and disaster recovery fallback.
In case GitHub becomes unavailable, GitLab should be promotable to the primary source of truth with minimal disruption.
Scope
- Configure repository mirroring from GitHub to GitLab
- Ensure all branches and tags are synchronized
- Replicate release artifacts where applicable
- Set up a reliable sync mechanism (scheduled is fine)
DeepFace Weights:
- Include backup and synchronization of DeepFace model weight files (e.g., .h5)
- Store weights in a scalable and reliable location (e.g., GitLab Package Registry or alternative storage)
- Ensure weights are accessible independently of GitHub availability
- Implement logic to fetch model weights primarily from GitHub. If fetching from GitHub fails (e.g. 404), automatically fallback to GitLab source
- You don't have a ci cd in the mirroring repo
Notes:
- Use read-only access tokens where applicable
- Avoid storing large binaries directly in the repository; prefer package registry or artifact storage
Additional Info
No response
Source: serengil/deepface