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
Documentation for manual GeoIP updates needs more info #15638
Comments
Ok. Actually it would be expected to have those files working directly. |
Hmmm. Okay, I think that this was because I didn't have the GeoIP2 plugin enabled. On activating this it found the file, but the legacy pear plugin didn't see it (because it's an mmdb file now rather than the .dat file that I was replacing?) edit: Actually, you're right, it has to be a specific name, even with the GeoIP2 plugin activate. This should certainly be in the docs if it's not just going to load any mmdb file from the directory. |
On the subject of activating plugins via the UI. I would have thought that the Plugins and PluginsInstalled would be better placed in the DB or something. I'm configuring matomo with puppet and because our production infrastructure is a load balanced trio of servers, and a separate DB, these interface changes get wiped out by puppet because the file has changed. Matomo have made some concessions to this with the Here's an example of what changes in the config file after a puppet run after activating GeoIP2 via the UI:
|
Hi @tsteur I think that the documentation needs updating to let us know what to name the files. It seems that not just any .mmdb will work, it has to have a specific name. I just extracted mine to be edit: Although I might have got this working if I had known about the GeoIP2 plugin earlier as I did find references in the code to this and some other names |
I updated the FAQ entry to be more explicit and the rest should be already in #6063, so we can close this. |
From the documentation on this page:
But it doesn't tell you what filename to extract it out as. I tried to read the php but the code is highly obfuscated making it impossible for me to determine what is an acceptable DB name. Extacting the file from the gz gives today, for example,
dbip-city-lite-2020-02.mmdb
.The text was updated successfully, but these errors were encountered: