The GeoNode docker images built with this solution differs in with the standard images. Normally a different entry point should be called (stored in /usr/src/my_project/entrypoint.sh) and the tasks.py used for the invoke command is the one stored in /usr/src/my_project/tasks.py).
Since the K8s custom tasks.py is mounted on /usr/src/geonode/tasks.py, when used with the custom images, it is not taken into account.
Proposed Solution
A first solution could be to be able to configure the mount path of the tasks-py volume. Perhaps there are other differences to investigate.
Additional Information
Any additional information or context that may be helpful in implementing the feature.
Feature Description
One of the recommended way to deploy GeoNode is to create a GeoNode project based on the GH repo https://github.com/GeoNode/geonode-project.
The GeoNode docker images built with this solution differs in with the standard images. Normally a different entry point should be called (stored in /usr/src/my_project/entrypoint.sh) and the tasks.py used for the invoke command is the one stored in /usr/src/my_project/tasks.py).
Since the K8s custom tasks.py is mounted on /usr/src/geonode/tasks.py, when used with the custom images, it is not taken into account.
Proposed Solution
A first solution could be to be able to configure the mount path of the tasks-py volume. Perhaps there are other differences to investigate.
Additional Information
Any additional information or context that may be helpful in implementing the feature.