[DO NOT MERGE] -- location-based ip blocking

[ali123]

@jbau please take a look

[jbau]

will do.
To any community members watching this: nothing is imminent about blocking, especially at edx.org. This is just backup code for just-in-case, at Stanford

[jbau]

looking now. first you should add "pygeoip==0.3.0"
to requirements/edx/base.txt

[jbau]

License for pygeoip is License: LGPLv3+

[jbau]

would making this a part of the module, instead of part of the class, be more efficient?

[jbau]

actually, I think this is okay. it's in the class prototype.

[carsongee]

Just my2cents, but why not just do the blocking with nginx or apache? It seems simpler and more configurable than adding it inside the platform. http://nginxlibrary.com/ip-based-country-blocking/ for nginx example.

[jbau]

that approach has merits for sure--do we need to compile our own nginx to do that?

[carsongee]

nginx -V on my vanilla sandbox install it has the geo_ip module baked in.

[jbau]

Nice!

On Feb 7, 2014, at 9:29 AM, Carson Gee notifications@github.com wrote:

nginx -V on my vanilla sandbox install it has the geo_ip module baked in.

—
Reply to this email directly or view it on GitHub.

[jbau]

@ali123 it also looks like you need to do a similar envs setup for cms

[jbau]

can you also move the middleware into its own file? some import sequences used by the "gather-assets" step of prod install load util.requests and actually instantiates the middleware class, but the files and settings referred to by that class aren't always there.

[jbau]

oh hmm: https://docs.djangoproject.com/en/1.4/ref/contrib/gis/geoip/

[singingwolfboy]

This pull request hasn't been touched in a month, it needs a rebase, and the title is marked "DO NOT MERGE". Can this pull request be closed, or is it still being used for something?

[ali123]

@singingwolfboy I'm closing this PR. We've implemented it at nginx level.