-
Notifications
You must be signed in to change notification settings - Fork 0
Harden featureService #21
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
Conversation
scripts/install.sh
Outdated
| # setup | ||
| build_dependencies='curl git build-essential' | ||
| sudo apt-get update > /dev/null | ||
| sudo apt-get upgrade > /dev/null |
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.
Add -y to this line to avoid blocking on user input.
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.
Yep, got it locally, just need to push it.
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.
See 26fc2f1
anthturner
left a comment
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.
LGTM.
One minor note is that fail2ban uses iptables by default IIRC, so we should verify that bringing up iptables via fail2ban doesn't overzealously block access to anything else on the server (like the nodejs app).
|
Already tried this on a deployment and everything seems to be working fine :) http://fortis-features.eastus.cloudapp.azure.com/features/name/bogota Thanks for the review! |
See CatalystCode/project-fortis-pipeline#239: