Persist GeoNode log in volume

[giohappy]

Following the discussion in https://github.com/GeoNode/geonode-project/issues/266 we want to do an initial improvement by

• saving the geonode log and the celery log to a persistent volume. I would consider the option to create a new logs, where we might decide to persist also the logs from geoserver afterward.
• (optional) assess a mechanism to redirect to stdout stderr as we do for the invoke.log.

Regarding the latter point, I don't know if it would make sense to make this option log both to the log file AND stdout. @randomorder @afabiani opinions on this?

[randomorder]

Hi @giohappy I agree on having a dedicated volume for the logs and persist the logs on disk. We can have either invoke.log OR geonode.log on stdout / stderr but I wouldn't redirect both, it wouldbe messy IMO

Regarding the latter point, I don't know if it would make sense to make this option log both to the log file AND stdout.

I would prefer one OR the other with default on file and an override

[giohappy]

I would prefer one OR the other with default on file and an override

ok, in that case we can have two more env variable similar to the INVOKE_LOG_STDOUT. It might be GEONODE_LOG_STDOUT and CELERY_LOG_STDOUT

[jkariscodes]

Having created the logs successfully and

1. Inspecting the logs volume I have the following.
2. Listing contents in the volume shows celery and geonode logs present. I noted that Nginx logs are being outputted in stderr as shown below.

[giohappy]

@jkariukidev please create the issue upstream and the PR (notice my comment here)