-
Notifications
You must be signed in to change notification settings - Fork 60
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
Readd Crowdsec Bouncer #8
base: master
Are you sure you want to change the base?
Conversation
Ok this is done can you redo the build since 0.1.11 was just released, my testing now shows the memory usage back to normal levels of 100mb-200mb for my 7 Vhosts |
This will also require a change in the main project for the config files as well |
Can't pull the above due to permissions but i have built a docker image my side, #8 https://hub.docker.com/r/lepresidente/nginxproxymanager:latest I have been using this for the past month with no issues |
Hello, what is the status on this PR? My understanding is that the feature request was merged-and-reverted due to a memory leak, but the memory leak has since been fixed based on op's description in this PR. |
fixed merge conflicts |
@jc21 Any update on Readding this and going forward with this change? |
Is there any additional testing (or otherwise) I can possibly help with in order to see this PR merged by chance? |
Docker Image for build 223 is available on DockerHub as:
|
Up |
Re add the crowdsec nginx bouncer
Requires upstream change first crowdsecurity/cs-openresty-bouncer#28, will bump the version once its been released and remove the ONHOLD from the title.