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

Can I use it with Wordpress? #11

Closed
robert1112 opened this issue Mar 29, 2018 · 5 comments
Closed

Can I use it with Wordpress? #11

robert1112 opened this issue Mar 29, 2018 · 5 comments

Comments

@robert1112
Copy link

Hi Is there easy way to use it with Ngxin and wordpress? Thank you.
@jiangwenyuan
Copy link
Owner

jiangwenyuan commented Mar 29, 2018 •
edited
Loading

Hi @robert1112

Yes, you can use it with (Nginx and) wordpress, and I think the setup is quite easy.

@robert1112
Copy link
Author

Hi @jiangwenyuan
Nice to hear from you so soon! We got a HAProxy in the front of Nginx. And how will the user purge the cache from Wordpress directly from Wordpress dashboard without a wordpress plugin? Is there further caution/ advice I can take from you? Thank you.

@jiangwenyuan
Copy link
Owner

Hi @robert1112

I'm not familiar with wordpress dashboard, basically purging cache is done by making HTTP PURGE or POST requests, as long as you can make HTTP request in dashboard, I think you can purge cache without plugin.

@robert1112
Copy link
Author

Okay I will see it can be pulled off. Thank you so mcuh for your excellent work.

@jiangwenyuan
Copy link
Owner

Not at all, feel free to fire any issues

jiangwenyuan pushed a commit that referenced this issue Dec 9, 2019
@haproxyFred @wtarreau
MINOR: log: Add "sample" new keyword to "log" lines.
d95ea28 
This patch implements the parsing of "sample" new optional keyword for "log" lines
to be able to sample and balance the load of log messages between serveral log
destinations declared by "log" lines. This keyword must be followed by a list of
comma seperated ranges of indexes numbered from 1 to define the samples to be used
to balance the load of logs to send. This "sample" keyword must be used on "log" lines
obviously before the remaining optional ones without keyword. The list of ranges
must be followed by a colon character to separate it from the log sampling size.

With such following configuration declarations:

   log stderr local0
   log 127.0.0.1:10001 sample 2-3,8-11:11 local0
   log 127.0.0.2:10002 sample 5:5 local0

in addition to being sent to stderr, about the second "log" line, every 11 logs
the logs #2 up to #3 would be sent to 127.0.0.1:10001, then #8 up tp #11 four
logs would be sent to the same log server and so on periodically. Logs would be
sent to 127.0.0.2:100002 every 5 logs.

It is also possible to define the size of the sample with a value different of
the maximum of the high limits of the ranges, for instance as follows:

   log 127.0.0.1:10001 sample 2-3,8-11:15 local0

as before the two logs #2 and #3 would be sent to 127.0.0.1:10001, then #8
up tp #11 logs, but in this case here, this would be done periodically every 15
messages.

Also note that the ranges must not overlap each others. This is to ease the
way the logs are periodically sent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jiangwenyuan @robert1112