[GeoNode-devel] Practices on maintaining a geonode project, PR: "Align to GeoNode master 4.2.0"

[Henning Bredel]

Dear GeoNode community,

I just read the pull requests "Align to GeoNode master (4.2.0) and 
improve/fix docker initialization" on geonode-project [0] and geonode 
upstream [1].

They include a lot of good changes on configuration and Docker setup. I 
added my question as a comment [2], but we may discuss this right here, 
as well.

What are your experience on using geonode-project, in particular with 
regard on updating it to use a new GeoNode version? To my understanding, 
you would have to track the commits since your project initialization 
and apply all the changes manually. Is there better way to maintain a 
geonode-project, and do you have good reasons to prefer geonode-project 
over a simple geonode fork?

Looking forward to read your opinions and shared experience.

Thanks

   Henning

[0] https://github.com/GeoNode/geonode-project/pull/457
[1] https://github.com/GeoNode/geonode/pull/11308
[2] 
https://github.com/GeoNode/geonode-project/pull/457#issuecomment-1658028740
-- 
Henning Bredel
52°North Spatial Information Research GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: h.bredel at 52north.org
http://52north.org/
Twitter: @FiveTwoN
Managing Directors:
Dr. Benedikt Gräler, Dr. Simon Jirka, Matthes Rieke
Local Court Muenster HRB 10849
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20230731/0d81801b/attachment.sig>