-
Notifications
You must be signed in to change notification settings - Fork 84
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
Add option for http_cache_hosts #697
Comments
Hi @phoenix-bjoern , did you try extending this via scenarios? If it's a single command to be done during deploy, you may be able to add it via scenarios for now, since we cannot add it natively to main scenario until we have good ways of testing it and running in production. See this: https://devdocs.magento.com/cloud/deploy/scenario-based-deployment.html |
@YPyltiai thanks for the feedback. Of course this would be doable. However I think this is a missing feature as Varnish is the default FPC on-premise and in order to invalidate cache elements the setting in env.php is required. IMHO support in ece-tools is a must-have. |
@phoenix-bjoern it makes sense - my only comment is about the design part of it. Current flows are specific to Cloud and we added scenario concept to allow for out of Cloud customization. We just need to think if we just do the variable here to control it or fork scenario & extend it for Varnish support there (out of Cloud scenario). We should accept PR but let's discuss this design question first. Let me tag few people here. @NadiyaS , @shiftedreality , @kandy - what do you guys think? |
I would like to suggest leaving this functionality in |
@shiftedreality @YPyltiai We can either use
|
Hi @phoenix-bjoern |
@phoenix-bjoern is this request still actual? |
Yes, it is and I would be happy if this gets option gets supported in ece-tools. |
To enable Varnish in env.php an additional command needs to be executed:
bin/magento setup:config:set --http-cache-hosts=varnish
It seems there is no possibility to append
to env.php in ece-tools.
The text was updated successfully, but these errors were encountered: