Opened 6 years ago
Closed 6 years ago
#29875 closed New feature (invalid)
Support GeoLite2 databases
| Reported by: | Tom Forbes | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | 2.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
MaxMind is deprecating the GeoLite database (see https://dev.maxmind.com/geoip/legacy/geolite/). They are pushing people towards the GeoLite2 databases.
The geodjango docs should be updated and we should ensure that we work with both GeoLite2 and GeoLite databases.
Change History (4)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
The geoip2 docs already reference GeoLite2. Those are the files that Jenkins is using. Did I miss something about what needs to be done?
comment:3 by , 6 years ago
Oh, right. I must have been reading the 1.11 docs when I made this ticket. Sorry!
As 1.11 is going to be maintained past the time when GeoLite will be removed from their website, is it worth backporting this or adding some kind of note to the docs?
Note:
See TracTickets
for help on using tickets.
After reading some of the documentation and code the underlying
geoip2library we use *should* be compatible. We'd need to update the docs to point to the new geolite2 releases and update the testing infrastructure to use it.