Skip to content
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

Questions about using MaxMind's GeoIP2 GeoLite2 Country, City, and ASN databases #392

Closed
crashzk opened this issue Mar 28, 2024 · 2 comments
Labels
untriaged New issue has not been triaged

Comments

@crashzk
Copy link

crashzk commented Mar 28, 2024

Some plugins use these databases: https://github.com/P3TERX/GeoLite.mmdb

However, all plugins you use need to place these databases in the plugin folder in question.

I would like to know if it would be interesting to include this database in CSSharp directly? A folder where these databases would be located and the plugin you need just searches there. This way we can avoid multiple database versions, one for each plugin.

It could be located in the addons/counterstrikesharp/configs/geoip folder

Or there would be a reason for how it works now, so it wouldn't be possible to change it.

@github-actions github-actions bot added the untriaged New issue has not been triaged label Mar 28, 2024
@roflmuffin
Copy link
Owner

Plugin authors can place and use these from the shared folder (at the same level as plugins), but there isn't any plans to ship this with the framework

@crashzk
Copy link
Author

crashzk commented Mar 30, 2024

I understand, I think it would be quite impractical for me to have to update folder by folder with these GEOIP in all the plugins I use whenever there is an update to these databases, so leaving something "centralized" would be interesting.

Anyway, thanks for the explanation.

@crashzk crashzk closed this as completed Mar 30, 2024
@crashzk crashzk closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2024
@crashzk crashzk reopened this Mar 30, 2024
@roflmuffin roflmuffin closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

2 participants