Conversation
27e536e to
c9047ea
Compare
c9047ea to
f2162c1
Compare
25908fc to
69558c2
Compare
|
Back to passing, cleaned up and with last push it works locally as well again, super fast as always. /cc @bdunogier How to tests (same exact steps as .travis.yml to know where to look next time you want to try):
|
|
For readability, I'd suggest we split the ci/docker changes from the VCL ones (more like doc). I can do it, @andrerom, just let me know. |
|
From what I've seen, the VCL looks good. Haven't really looked at the docker part :) |
69558c2 to
956e7c2
Compare
Should be easier now, just removed the duplicated vcl in entrypoint folder :D |
| return (synth(405, "Method not allowed")); | ||
| } | ||
|
|
||
| # If http header "xkey" is set, we assume purge is on key and you have Varnish xkey installed |
There was a problem hiding this comment.
Align header name to be same on occurances here, in kernel and on foshttpcache pr, afaik it should be "key" like on line below and in foshttpcache
| # docker-compose exec varnish varnishlog -g request -q "ReqMethod eq 'PURGE'" | ||
| # | ||
| # But before doing that check that http and not local purge client is set: | ||
| # docker-compose exec app app/console --env=dev debug:container ezpublish.http_cache.purge_client |
There was a problem hiding this comment.
Needs to be adapted to the service used by the http-cache package.
There was a problem hiding this comment.
What does it need to be now?
| "incenteev/composer-parameter-handler": "~2.0", | ||
| "tedivm/stash-bundle": "~0.4", | ||
| "ezsystems/ezpublish-kernel": "~6.7@dev", | ||
| "ezsystems/ezpublish-kernel": "dev-feature-EZP-25696 as 6.7.x-dev", |
There was a problem hiding this comment.
To be replaced with the enablement of the EzSystemsPlatformHttpCacheBundle in the AppKernel.
|
Given that the feature has been merged to ezsystems/ezplatform-http-cache, it has been decided that the VCL would go into the new package. I'll push a new version without the VCL changes. The Docker ones only make sense in this repository, don't they ? I suggest that we leave the current varnish configuration untouched in this repository, and update the documentation to mention the external package and corresponding documentation. |
yes, they only make sense here.
@bdunogier For 1.8 yes But I think I'll leave this PR open with aim to at some point have official Varnish container, and ideally it should use the xkey variant of the VCL, so guess it will have to wait for version where we switch the default. |
a571119 to
57e6b34
Compare
Varnish changes, ezplatform-http-cache package (uses varnsh xkey for improved varnish performance, and cache ability of our REST api++).
Todo:
ezplatform-http-cacheis the default