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
As we are developing other Geonodes for the Resilience Academy, we would like to work on the idea of using the same Geoserver but connecting more than one Geonode. This way, we don't make many servers instead just add more space to the current server but still be able to use more than one Geonode. I am attaching a diagram to explain this. Resilience Academy Geodatabase infrastructure.pdf
The text was updated successfully, but these errors were encountered:
As I mentioned during the call this is a significative change to the GeoNode codebase.
If you agree, I would want to ask our team here to make an estimate with a technical proposal.
Hi @msilikale05,
the above meas, that I do not know at this stage.
We need to investigate a little and make an estimate to give you an answer; my gut feeling is that 15 days might be just enough, but this depends also on how we plan to tackle this limitation and I would want to avoid doing quick workarounds for this.
To make it clearer, can we use up to 1 days out of the pool to prepare an estimate as well as technical plan?
As we are developing other Geonodes for the Resilience Academy, we would like to work on the idea of using the same Geoserver but connecting more than one Geonode. This way, we don't make many servers instead just add more space to the current server but still be able to use more than one Geonode. I am attaching a diagram to explain this.
Resilience Academy Geodatabase infrastructure.pdf
The text was updated successfully, but these errors were encountered: