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

Code to pass hostname to Varnish and optimally only purge the current domain. #4905

Closed
wants to merge 3 commits into from

Conversation

pynej
Copy link

@pynej pynej commented Jun 6, 2016

pynej added 3 commits June 6, 2016 15:23
Add code to forward the hostname to varnish when purging the cache.
Add code to read hostname and sample code to only purge current domain.
Added code to track hostname and sample code to purge only the current domain.
@okorshenko
Copy link
Contributor

HI @pynej Unfortunately we can not accept this PR. In current implementation it is incompatible with latest changes in develop branch. Please reopen this PR once ready for delivery. Thank you

@okorshenko okorshenko closed this Jun 30, 2017
@okorshenko okorshenko self-assigned this Jun 30, 2017
@okorshenko okorshenko added this to the June 2017 milestone Jun 30, 2017
@pynej
Copy link
Author

pynej commented Jun 30, 2017

Yah, I'm not going to be doing that as I reported the issues and patch over year ago.

@woutersamaey
Copy link
Contributor

Another community powered improvement gone to waste.

@okorshenko
Copy link
Contributor

Hi @woutersamaey as I said we can not accept broken code to mainline. This is good improvement, but it must work. Please, let us know If you would like to proceed with this PR. We will do our best to help you. Thank you.

@woutersamaey
Copy link
Contributor

I understand you have a process in place @okorshenko, but it's just not working.
I see a lot of important improvements just lying around for over a year. This is no exception.

Essential stuff, you should care about. But instead you want us to do all the work. It's just not a group effort.

Now assume that @pynej fixes this issue, you may or may not accept the PR. And when it is finally accepted, it may still be another year before we see it in a release and can actually benefit from his work.

At least this is the impression that I got from many essential improvements and bug fixes lying around.

The current process is not working as it should be. You should put developers on these issues to help out, work we contribute should end up in a release no more than 3 months after it was made and you should publish statistics so that people can actually see the community and process work and regain confidence.

When we start out a project, we run into issues. Old issues, that have been fixed most of the time already. Instead, we keep fighting old fights, which is downright depressing.

There's also a reason i say 3 months, because most projects take this long. When we contribute, we should get our own improvements in a timely fashion.

Now, we're disconnecting, losing interest like @pynej

Don't forget it's the developers that make the community.

Ps: Sorry for going on like this. I'm very passionate about Magento and would love to see improvements in this key area.

magento-engcom-team pushed a commit that referenced this pull request Oct 17, 2019
[TSG-Commerce] Tests for 2.3 (pr1) (2.3-develop)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants