Open alexanderfschley opened 4 years ago
Hello @alexanderfschley, thanks for opening this issue. Do you think you could provide this documentation, or would you need others to create it? Youre well written issue descriptions seems like you have already gathered a lot of knowledge here, thats the reason I ask.
Hello @gannebamm . Honestly, I will need others to be able to provide this documentation. I'm starting to study Geonode and I still don't have a thorough knowledge of the python language. I opened this issue due to the difficulty in solving this specific problem. But nothing prevents me from being able to help in other situations. I am really inspired to delve into the tool.
Ok, than letΒ΄s tackle this issue together π
I am quite busy with other things these days - but will start looking into it later this week / at the weekend.
Hey, I am starting to look into updating some of this, too. I mostly understand, but what is wrong with the GEOIP_PATH
? I am missing that part.
There are some various other discrepancies I notice in the monitoring docs I'll try to update as well.
Another thing is I believe the entire Configuration
section is covered by the fixture metric_data.json
? It appears for me that all that is automatically registered via this fixture, so I can update it just to say to double check.
Finally, the only things left I'm not sure I understand in the current docs is these two bullet points:
Sites
from admin; make sure it contains a correct host nameOtherwise I'll make updates from what I do know, but if anyone can clarify those few questions, I can add that too. Thanks :)
@travislbrundage Great! Unfortunately, I am not much familiar with the monitoring app but would suggest starting the official docker stack as a reference. as far as I remember it is set up there working well.
update Sites from admin; make sure it contains a correct host name
Might be the django site configuration. See an example from master.demo
do not forget to enable notifications and configure them from user profile
I think this could be this part: https://docs.geonode.org/en/master/usage/accounts_user_profile/updating_profile/notification_settings.html#setting-notification-preferences
Hey, I am starting to look into updating some of this, too. I mostly understand, but what is wrong with the GEOIP_PATH? I am missing that part.
Geoip is the IP Adress to regions database which is used to map the requests to countries in the monitoring app. Due to policy changes we had to change the Geoip database. There is some closed issue in this repo covering it, but I am unable to find it adhoc.
BTW great you tackle this πππ
An update of the monitoring documentation would be relevant for an intuitive installation to occur and also for being an essential functionality. All steps in Geonode Core suggest using
geonode.local_settings
, unlike the Internal Monitoring Application, which usesgeonode.settings
. In addition, in the monitoring documentation,GEOIP_PATH
is set toGeoIPCities.dat
as the default and the current format isGeoLite2-city.mmdb
. AlsoMONITORING_SERVICE_NAME
is defined as the defaultlocal-geonode
, and in Django Administration it provides services with the namelocalhost-hostgeoserver
,default-geoserver
,localhost-hostgeonode
andgeonode
.