Stop using Git forges as CDNs for component sources #471
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform#471
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Component fetches are unreliable during deployment and testing. Codeberg returned HTTP 429 errors, and fetching Bootproof from containerfiles also failed. GitHub mirrors and fallback behavior help for now, but Git forges should not be the long-term CDN for component sources.
Proposed direction
Evaluate serving component sources through the CDN already running in our Kubernetes cluster alongside our Forge, rather than building a separate solution. Coordinate this with the planned platform bootstrap and CI/CD setup. This issue is for tracking; migration is not planned immediately.
Next steps