-
Notifications
You must be signed in to change notification settings - Fork 397
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
Is acquia.inc an appropriate file to include in this repo? #384
Comments
It looks like there's some code in |
My thoughts are that it should be a middleware service, separate configuration from functionality. Core has the Ban module which allows limited IP blacklisting. It stores IPs in a table and performs queries in the middleware, so I would think checking configuration would pose no problems. If done as a service it should be a module and could be added via composer during install? |
I guess I would suggest that if it's an Acquia recommendation for protecting your environment, it makes sense to add it into the acquia (sort of?) framework. The approach has the file included into your settings.php and configured there, so it could make sense to add it to I don't personally mind too much if it doesn't make it in there, as we can keep it in our repo. I think adding it to the repo gives a great way to open source contribute to the file though. If I have a chance, I could stage a PR for review & critique at some point, if it's even a road to go down. |
Yeah I agree that it makes more sense as middleware than as part of BLT. Though, I'd be happy to add it as a default dependency for new BLT projects. |
Does this make sense here? It's an example file that loads `/sites/default/settings/envprotect.settings.php`, which is a file that does not exist in BLT. Per discussion in acquia#384, the functionality that this file is referencing was decided to make more sense as middleware.
Does this make sense here? It's an example file that loads `/sites/default/settings/envprotect.settings.php`, which is a file that does not exist in BLT. Per discussion in #384, the functionality that this file is referencing was decided to make more sense as middleware.
Many Acquia customers use this or the D7 version to protect their site/paths. Is BLT a suitable place to have this also included.
As a sidenote to this, it's been raised to me that this could potentially be a D8 Middleware service. Thoughts from smarter people are welcome in this question too.
The text was updated successfully, but these errors were encountered: