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.

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

feat: add varnish WIP #1961

Closed
wants to merge 1 commit into from
Closed

feat: add varnish WIP #1961

wants to merge 1 commit into from

Conversation

Chris53897
Copy link
Contributor

This is just a proof of concept for varnish with APIP 2.6.
It is buggy. /docs need sometimes refreshed 4-6 times to work.
PWA, Vulcain, Mercure is not supported (or tested) at the moment.
I try to reuse varnish code from apip 2.5.

You may want to change these lines for your platform in /api/Dockerfile
#FROM varnish:${VARNISH_VERSION} AS api_platform_varnish

only temp for develop on Mac M1 - ARM64 not available for org. varnish

FROM beevelop/varnish AS api_platform_varnish

I am working on the deployment for kubernetes. Varnish is called but could not cache invalidation working.
Until this is fixed i am not gone push that.

@vincentchalamon
Copy link
Contributor

vincentchalamon commented Jul 20, 2022

Hi @Chris53897

Thanks for this proposal. If this POC is still in progress, have you considered Souin as a Caddy cache-handler instead of Varnish?

@Chris53897
Copy link
Contributor Author

Hi @vincentchalamon
Unfortunately No. This PR/Topic priority has been lowered by company. And i changed company at the meantime.
Add the time of implementing i had a look at https://github.com/caddyserver/cache-handler But there was a lot of WIP and missing features. That was the reason i tried it with varnish.

@dunglas
Copy link
Member

dunglas commented Jul 20, 2023

Closing in favor of #2383.

@dunglas dunglas closed this Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants