-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Added real IP and block IP functionality. #714
Conversation
We could merge like this but I'm fairly certain nginx needs a reload signal to pick up the changes. So a normal deploy probably wouldn't do the trick. We could add a command step after this (similar to |
If we ever wanted to hide the IPs or share with ingest we could put an s3 object somewhere and build the list from that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be fine merging this. As you noted, it won't be perfect w/o some plan on reloading or config sharing. But we can iterate.
@matschaffer |
Yep
On Tue, Jul 14, 2020 at 16:55 Andrew Todd ***@***.***> wrote:
@matschaffer <https://github.com/matschaffer> web.config already contains service
nginx restart, will that execute again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#714 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAFMVBIG2P7AXFIYW2YMLR3QFPXANCNFSM4OZHWTKA>
.
--
…-Mat
matschaffer.com
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t understand much in it, so I’ll just go ahead and approve, hehe
I'm going to make another build with my own IP address in the block list and deploy that to make sure it works, then will merge. |
Bit of confusion, I was pushing to the wrong config directory, but after that's fixed I've confirmed that a redeploy to the same environment should update the blocklist. |
Related to issue #648
Based on research from @ZacharyCChang0828
This will enable us to block IP addresses or CIDR ranges by modifying the
web.config
file and redeploying.I have manually applied these changes in dev, so I know that the config works, but I'm not sure the
.ebextensions
syntax is correct.Risks:
Follow-up tasks:
.ebextensions
change. I'm not sure an ordinary deploy will do it.