You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
I have to use a dockerized geonode 4.1.2 but with an external DB. I have changed the .env file accordingly and the Geoserver stores but the geofence kept not working.
After some research, I found that I can edit the file /templates/geofence/geofence-datasource-ovr.properties.j2 in the geonode/geoserver container so to override the file geofence-datasource-ovr.properties in the geoserver datadir, but this file is part of the image.
This is the initial value of geofenceDataSource.url in the file with the database host "db" hardcoded: geofenceDataSource.url=jdbc:postgresql://db:5432/{{ GEONODE_GEODATABASE }}
I want to make the database host as a parameter from the .env file by replacing the geofenceDataSource.url with the following one :
I have to use a dockerized geonode 4.1.2 but with an external DB. I have changed the .env file accordingly and the Geoserver stores but the geofence kept not working.
After some research, I found that I can edit the file
/templates/geofence/geofence-datasource-ovr.properties.j2
in the geonode/geoserver container so to override the filegeofence-datasource-ovr.properties
in the geoserver datadir, but this file is part of the image.This is the initial value of
geofenceDataSource.url
in the file with the database host "db" hardcoded:geofenceDataSource.url=jdbc:postgresql://db:5432/{{ GEONODE_GEODATABASE }}
I want to make the database host as a parameter from the .env file by replacing the
geofenceDataSource.url
with the following one :geofenceDataSource.url=jdbc:postgresql://{{ DATABASE_HOST }}:5432/{{ GEONODE_GEODATABASE }}
Please could you release a new version of the image with this edit, as I don't have access to the source code of image geonode/geoserver:2.23.0
The text was updated successfully, but these errors were encountered: