Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Setup CDN to proxy/cache all sites/artifacts #1507

Closed
setchy opened this issue Sep 25, 2023 · 2 comments
Closed

Setup CDN to proxy/cache all sites/artifacts #1507

setchy opened this issue Sep 25, 2023 · 2 comments
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@setchy
Copy link

setchy commented Sep 25, 2023

Copied from Slack discussion

I think we need a project to set up a CDN such as through cloudflare which proxies/caches all the the sites/artifacts which containerbase might use. Maybe with cloudflare workers we can make it “serverless”. Then we could default containerbase builds to use this cdn by default, including for apache.

If we use https://developers.cloudflare.com/cache/advanced-configuration/cache-reserve/ then it should be a “permanent” store and be able to serve content even if the upstream goes down or rate limits
@rarkins
Copy link
Member

rarkins commented Sep 25, 2023

I've registered containerbase.dev just now and propose we aim to use cdn.containerbase.dev

@viceice viceice added type:feature Feature (new functionality) priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started labels Oct 12, 2023
@viceice
Copy link
Member

viceice commented Oct 12, 2023

Duplicate of #972

@viceice viceice marked this as a duplicate of #972 Oct 12, 2023
@viceice viceice closed this as completed Oct 12, 2023
@viceice viceice mentioned this issue Oct 12, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@setchy @viceice @rarkins