From florian.hoedt at thuenen.de Thu Apr 8 03:33:19 2021 From: florian.hoedt at thuenen.de (Florian Hoedt) Date: Thu, 8 Apr 2021 12:33:19 +0200 (CEST) Subject: [GeoNode-devel] How to connect / synchronize two GeoNode Instances Message-ID: <1049869672.848556.1617877999459.JavaMail.zimbra@thuenen.de> Hi Developers, We want to connect / synchronize multiple GeoNode instances. For example one instance is open for external project partners, our main instance is only for internal usage. The idea is to pull layers and documents into the main instance. Are there good and proven ways to do so? yours, Florian -- MSc Florian Hoedt Head Geoinformatics | OpenData Representative Th?nen Institute, Centre for Information Management Bundesallee 44 38116 Braunschweig Tel: +49 531 596-1428 Mobil: +49 162 92 50 275 Fax: +49 531 596-1499 Mail: florian.hoedt at thuenen.de Web: www.thuenen.de The Johann Heinrich von Th?nen Institute, Federal Research Institute for Rural Areas, Forestry and Fisheries ? Th?nen Institute in brief ? consists of 14 specialized institutes that carry out research and provide policy advice in the fields of economy, ecology and technology. From alessio.fabiani at geo-solutions.it Thu Apr 8 06:19:06 2021 From: alessio.fabiani at geo-solutions.it (Alessio Fabiani) Date: Thu, 8 Apr 2021 15:19:06 +0200 Subject: [GeoNode-devel] How to connect / synchronize two GeoNode Instances In-Reply-To: <1049869672.848556.1617877999459.JavaMail.zimbra@thuenen.de> References: <1049869672.848556.1617877999459.JavaMail.zimbra@thuenen.de> Message-ID: Hi Florian, for some of our customers we use the GeoNode backup/restore mechanism inside the docker containers along with Jenkins [image: image.png] I'm going to attach some advanced scripts we are currently using for this customer. They are almost the same present into the GeoNode core. Alessio. P.S.: notice that this fix is not included into the current GeoServer distribution for GeoNode, but this does not prevent BR to work Il giorno gio 8 apr 2021 alle ore 12:33 Florian Hoedt < florian.hoedt at thuenen.de> ha scritto: > Hi Developers, > > We want to connect / synchronize multiple GeoNode instances. For example > one instance is open for external project partners, our main instance is > only for internal usage. The idea is to pull layers and documents into the > main instance. Are there good and proven ways to do so? > > yours, > Florian > -- > MSc Florian Hoedt > Head Geoinformatics | OpenData Representative > Th?nen Institute, Centre for Information Management > Bundesallee 44 > 38116 Braunschweig > > Tel: +49 531 596-1428 > Mobil: +49 162 92 50 275 > Fax: +49 531 596-1499 > Mail: florian.hoedt at thuenen.de > Web: www.thuenen.de > > The Johann Heinrich von Th?nen Institute, Federal Research Institute for > Rural Areas, Forestry and Fisheries ? Th?nen Institute in brief ? consists > of 14 specialized institutes that carry out research and provide policy > advice in the fields of economy, ecology and technology. > _______________________________________________ > geonode-devel mailing list > geonode-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geonode-devel > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Alessio Fabiani @alfa7691 Founder/Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A - 55054 Massarosa (LU) - Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 331 6233686 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 74943 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: br.zip Type: application/x-zip-compressed Size: 2449 bytes Desc: not available URL: From alessio.fabiani at geo-solutions.it Fri Apr 9 02:54:10 2021 From: alessio.fabiani at geo-solutions.it (Alessio Fabiani) Date: Fri, 9 Apr 2021 11:54:10 +0200 Subject: [GeoNode-devel] Stability of branches during refactoring and cleanup In-Reply-To: References: Message-ID: Dear Adrian, please see below a first draft of the upcoming 3.2.0 release changelog Change Log3.2.0 (2021-04)Breaking Changes - Bump to postgresql-13 - Based on MapStore client 2.1.3 - MapStore client is no more compatible with 3.0.x train - ResourceBase Model BBOX now is a geometry; that is no more compatible with the 3.1.x one - GNIP-81: GeoNode Core Cleanup : - Removed GeoNetwork support - Removed QGIS-Server support - Removed SPC GeoNode support - Advanced Resources Publishing Logic has been revised (see below) Features - Python upgrade 3.7+ - Django upgrade 2.2.16+ - GeoServer upgrade 2.18.2 - MapStore2 Client Updates: - Save Search Services to the Map - Save Map Preferences into the adapter model - Advanced Style Editor with graphical UI - Improved Map Save Widget, specific for GeoNode - New MapStore client configuration subsytem - Upgraded Dokerfile and docker-compose to version 3.4 - Migration of CI from Travis to CircleCI - General Code Quality and Performance Improvements - Highlights GeoNode 3.2: - GNIP-76: Add RTL Support - GNIP-77: GetFeatureInfo Templating For GeoNode - GNIP-78: GeoNode generic "Apps" model to include pluggable entities into the framework - GNIP-79: GeoNode REST APIs (v2) - GNIP-82: Thesauri improvements - GNIP-83: ResourceBase for metadata-only resources - GNIP-84: Upload Page Enhancements - GNIP-85: Map legend - GNIP 86: metadata parsing and storing - Append data to an existing layer feature - Improved Metadata Editors, now able to handle HTML tags - Improved Catalog and Thesauri - Possibility to Upload RDF thesaurus via web - Pluggable CSW prefiltering from external apps - Delete existing table on restore command feature (general improvements to Backup/Restore machinery) - Advanced Upload Workflow Improvements: - Non admin user cannot change permission - Disable edit permissions globally when read-only mode is active - RESOURCE_PUBLISHING: 1. "unpublished" won't be visibile to Anonymous users 2. "unpublished" will be visible to registered users IF they have view permissions 3. "unpublished" will be always visible to the owner and Group Managers By default the uploaded resources will be "unpublished". The owner will be able to change them to "published" UNLESS the ADMIN_MODERATE_UPLOADS is activated. If the owner assigns unpublished resources to a Group, both from Metadata and Permissions, in any case the Group "Managers" will be able to edit the Resource. - ADMIN_MODERATE_UPLOADS: 1. The owner won't be able to change to neither "approved" nor "published" state (unless he is a superuser) 2. If the Resource belongs to a Group somehow, the Managers will be able to change the state to "approved" but NOT to "published". Only a superuser can publish a resource. 3. Superusers can do enything. - GROUP_PRIVATE_RESOURCES: The "unapproved" and "unpublished" Resources will be accessible ONLY by owners, superusers and member of the belonging groups. - GROUP_MANDATORY_RESOURCES: Editor will be FORCED to select a Group when editing the resource metadata. - Documentation Updates: - GetFeatureInfo Templating For GeoNode - HowTo: Geonode with QGIS - Improve GeoNode OpenID SP Protocol in order to be able to provide access to external clients - Document the use of slide show in themes - Update Advanced Installation steps to work against Ubuntu 20.04LTS - Update Advanced Installation steps to work against RHEL 7.x - How to setup rabbitmq, supervisor and memcached in order to fully enable async workers - How to Upgrade from 2.10.x / 3.0 - Docs to connect production docker to external postgreSQL db server - Documentantion for new metadata settings - Refers #6925: add documentation for thesaurus configuration - Refers #6952: add documentantion for uuidhandler - Adding new settings in order to let the optional metadata in metadata wizard to become required - Remove outdated/misleading SPC GeoNdoe documentation - Relates to #7089 Delete existing table on restore - Allow XSL customization - Relates to #7150 Doc for upload thesausus from admin interface - Relates to #7194 Append data to layer - Refers to #7214 Sorting Thesauri - Relates to #6995 Documentation for ADVANCED_EDIT_EXCLUDE_FIELD - Improving GeoNode Theme Library: introducing Jumbotron Slides - Implementation of an action to assign bulk permissions on layer to users selected from People and/or Group Django admin forms enhancement #6582 - Review of the current advanced resource workflow implementation enhancement security #6551 - File system operations do not adhere to Django file storage API enhancement in progress #6414 - Nav Toolbar gets distorted when multiple nav bar items are added by the admin enhancement frontend major #6412 - Allow only admins to edit/create keywords enhancement regression #6360 - In home page show only ISO categories currently assigned to some dataset enhancement frontend #6332 - Modify the admin theme customisation feature to allow for the use of a slide show in the home page enhancement feature frontend #6301 - Improve GeoNode OpenID SP Protocol in order to be able to provide access to external clients enhancement security #6273 - Limit "maps using this layer" to maps the user has permission to see enhancement security #6261 - Prevent integrity errors on singleton model save enhancement #6223 - Full list of Implemented GNIP - Full List of Implemented Features - Full list of Implemented Enhancements - Full list of Dependencies Updates - Full list of Fixed Security Issues - Full list of Fixed Security Pull Requests - Full list of Resolved Regressions - Full list of Fixed Critical Issues - Full list of Fixed Major Issues - Full list of Fixed Minor Issues - Full list of Updated Translations - All Closed Issues Full Changelog https://github.com/GeoNode/geonode/compare/3.1...3.2.0 Il giorno ven 19 mar 2021 alle ore 17:08 Alessio Fabiani < alessio.fabiani at geo-solutions.it> ha scritto: > Dear Adrian, > the changelog for 3.2.x is not yet complete. However I'm going to refresh > it during the we. You will be able to find the updated version here > > > The doc for upgrading is referring to the version 3.1 not the upcoming > 3.1.1 or 3.2.0, so unless you are going to upgrade to the stable 3.1.0 that > documentation might not be fully updated. > > I always suggest making a backup. If you are going to upgrade a production > instance the best practice is typically cloning it to a staging server, > upgrade, test and than switch the instances or repeat the upgrade steps > carefully. > > > Il giorno ven 19 mar 2021 alle ore 13:39 Adrian Bajer > ha scritto: > >> Thank you for your fast response! >> >> >> I have same additional questions regarding upgrade of my GeoNode >> instance: >> >> >> 1. I have GeoNode 3.0 (manually installed) running on a >> production-machine with Ubuntu 20.04LTS, GeoServer on a separate Tomcat, >> separate PostgreSQL/PostGis, using UWSGI daemon. >> If I want to upgrade to 3.1 or 3.2 should I follow that instruction: >> >> https://docs.geonode.org/en/master/admin/upgrade/index.html#upgrade-from-2-10-x-3-0 >> switching and aligning the source code and the requirements.txt to the >> 3.1.x branch? >> >> >> 2. Is it necessary to make data backup before upgrading? >> >> https://docs.geonode.org/en/master/intermediate/backup/index.html#full-geonode-backup-restore >> >> >> 3. Is there a Change Log for version 3.2? (I want to know what will be >> the most important changes in 3.2.) >> >> >> Best regards, >> >> *Adrian Bajer, MA* >> >> *Department of Historical Atlas* >> Institute of History, Polish Academy of Sciences >> >> Rynek Starego Miasta 29/31 >> 00-272 Warsaw, Poland >> e-mail: bajeradr at gmail.com >> >> >> pt., 19 mar 2021 o 12:52 Alessio Fabiani < >> alessio.fabiani at geo-solutions.it> napisa?(a): >> >>> Dear Adrian, >>> the branch 3.1.x is stable, we are backporting only few bug fixes and >>> minor improvements. >>> >>> I just tested it both running docker from the root geonode and >>> geonode-project and it works fine. >>> >>> 3.2.x is also relatively stable now, and we plan to release 3.2.0 soon. >>> However keep in mind that 3.2.x has breaking changes, so you might need to >>> do some manual work in order to adapt the old model to the new one. >>> There's no upgrade guide available yet around unfortunately, but the >>> process is not that hard (if you know how to do it). >>> >>> Just a big warning: both 3.1.x and 3.2.x are now relying a lot to >>> asynchronous architecture, so accordingly to how you deployed your old >>> versions, you might also install some new components as described here >>> >>> >>> https://docs.geonode.org/en/master/install/advanced/core/index.html#enabling-fully-asynchronous-tasks >>> >>> >>> You are still allowed to run everything synchronously, just pay >>> attention to your settings. >>> >>> Regards, >>> Alessio. >>> >>> >>> >>> >>> >>> Il giorno ven 19 mar 2021 alle ore 11:55 Adrian Bajer < >>> bajeradr at gmail.com> ha scritto: >>> >>>> Dear all, >>>> >>>> I need to upgrade instance of GeoNode in my Institute. Currently we >>>> have GeoNode 3.0 >>>> >>>> According to recent information about changes in branches I have some >>>> questions: >>>> >>>> 1. Which branch is stable if I want to install version 3.1? >>>> >>>> 2. When version 3.2 will be released? Maybe should I hold up my upgrade >>>> until 3.2 release? >>>> >>>> >>>> Best regards, >>>> >>>> *Adrian Bajer, MA* >>>> >>>> *Department of Historical Atlas* >>>> Institute of History, Polish Academy of Sciences >>>> >>>> Rynek Starego Miasta 29/31 >>>> 00-272 Warsaw, Poland >>>> e-mail: bajeradr at gmail.com >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------------------------------------------------------------- >>>> czw., 4 mar 2021 o 16:26 Alessio Fabiani < >>>> alessio.fabiani at geo-solutions.it> napisa?(a): >>>> >>>>> Dear devs, >>>>> branches created on: >>>>> >>>>> - geonode {3.2.x, 3.1.x} >>>>> - geonode-project {3.2.x, 3.1.x} >>>>> >>>>> deprecation messages put on: >>>>> >>>>> - geonode {3.x} >>>>> - geonode-project {3.x} >>>>> >>>>> documentation updated >>>>> >>>>> - documentation {master --> 3.2.x; 3.x --> 3.1.x} >>>>> >>>>> Moreover: >>>>> >>>>> geonode/geonode-project 3.2.x now point to geonode-mapstore-client >>>>> 2.1.x >>>>> >>>>> *WARNING 1: DO NOT USE MASTER BRANCH, IT WILL BE HIGHLY UNSTABLE* >>>>> >>>>> *WARNING 1: BUILD AND DEPLOYMENT TESTS STILL TO BE DONE ON NEW >>>>> BRANCHES 3.1.x; 3.2.x * >>>>> >>>> _______________________________________________ >>>> geonode-devel mailing list >>>> geonode-devel at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/geonode-devel >>>> >>> >>> >>> -- >>> >>> == >>> >>> GeoServer Professional Services from the experts! Visit >>> http://goo.gl/it488V for more information. >>> == >>> Ing. Alessio Fabiani >>> >>> @alfa7691 >>> Founder/Technical Lead >>> >>> >>> GeoSolutions S.A.S. >>> Via di Montramito 3/A - 55054 Massarosa (LU) - Italy >>> phone: +39 0584 962313 >>> fax: +39 0584 1660272 >>> mob: +39 331 6233686 >>> >>> >>> http://www.geo-solutions.it >>> http://twitter.com/geosolutions_it >>> ------------------------------------------------------- >>> >>> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >>> UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si >>> precisa che ogni circostanza inerente alla presente email (il suo >>> contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? >>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>> messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra >>> operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. >>> >>> >>> This email is intended only for the person or entity to which it is >>> addressed and may contain information that is privileged, confidential or >>> otherwise protected from disclosure. We remind that - as provided by >>> European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this >>> e-mail or the information herein by anyone other than the intended >>> recipient is prohibited. If you have received this email by mistake, please >>> notify us immediately by telephone or e-mail. >>> >> > > -- > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > Ing. Alessio Fabiani > > @alfa7691 > Founder/Technical Lead > > > GeoSolutions S.A.S. > Via di Montramito 3/A - 55054 Massarosa (LU) - Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 331 6233686 > > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra > operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. > > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Alessio Fabiani @alfa7691 Founder/Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A - 55054 Massarosa (LU) - Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 331 6233686 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From simone.giannecchini at geo-solutions.it Thu Apr 15 05:17:29 2021 From: simone.giannecchini at geo-solutions.it (Simone Giannecchini) Date: Thu, 15 Apr 2021 14:17:29 +0200 Subject: [GeoNode-devel] Upcoming Webinar for Release 3.2 of GeoNode Message-ID: Dear All, sorry for cross posting, I am sending this email to inform you that on 28th of April at 11 am eastern / 3pm GMT time we will hold a free webinar covering the upcoming 3.2 release of GeoNode. You can register here , you can find more information here . We hope to see you there! Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 https://www.geosolutionsgroup.com/ http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiara.sammarco at geodatalab.it Tue Apr 20 07:23:40 2021 From: chiara.sammarco at geodatalab.it (Chiara Sammarco) Date: Tue, 20 Apr 2021 16:23:40 +0200 Subject: [GeoNode-devel] Few questions about the current status (versions and branches) Message-ID: Hi all, I have a few questions about the current status of GeoNode. The first question is about geonode's installation versions, as far as I've understood: 1. SpcGeonode is no longer maintained. 2. There's a new docker version (in the guide). (About docker versions, I have noticed the geonode-project repo. Which is the difference?) 3. It is possible to follow a traditional installation (in the guide - installation for Ubuntu 20.04lts) Is that right? If you want to add something else to complete the picture, maybe it will be useful also for others. The last two options are normally maintained, aren't they? Is there a preferred one or I can freely choose the most convenient one? The second question is about branches. By reading the last messages in this mailing list, I have understood that branches 3.2.x or 3.1.x are more stable. Is that still like this? Thanks in advance for your help and suggestions. Best regards, Chiara Sammarco Technical Leader and Project Manager Via di Corticella, 315 | Bologna, BO 40128 tel (+39) 06 24 19 585 | mobile (+39) 342 19 60 662 www.geodatalab.it | management at geodatalab.it Nota di riservatezza: Questa email contiene informazioni private e/o confidenziali. Se hai ricevuto questo messaggio per errore sei pregato di eliminarlo e notificare il mittente. Grazie per la collaborazione. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rizky at kartoza.com Tue Apr 20 21:53:06 2021 From: rizky at kartoza.com (Rizky Maulana Nugraha) Date: Wed, 21 Apr 2021 11:53:06 +0700 Subject: [GeoNode-devel] Few questions about the current status (versions and branches) In-Reply-To: References: Message-ID: Hi everyone, I'm interested to follow the discussion. > SpcGeonode is no longer maintained. I didn't realize about this: SPCGeoNode was no longer maintained. Was this decision final? Will the recipes be excluded in the future from GeoNode repo? I've made some small patches into the scripts and docker-compose recipes in the past because it's very easy to customize deployment from those recipes. I even made Kubernetes Helm charts recipes based on SPCGeoNode recipes for our company, Kartoza. Was the reason SpcGeoNode no longer maintained because no one is actively working inside that directory? I've just realized that the SPCGeoNode section was no longer in the main/master docs. Regards, Rizky Maulana Nugraha On Tue, 20 Apr 2021 at 22:13, Chiara Sammarco wrote: > Hi all, > I have a few questions about the current status of GeoNode. > > The first question is about *geonode's installation versions*, as far as > I've understood: > > 1. SpcGeonode is no longer maintained. > 2. There's a new docker version (in the guide > ). > (About docker versions, I have noticed the geonode-project > repo. Which is the > difference?) > 3. It is possible to follow a traditional installation (in the guide - installation > for Ubuntu 20.04lts > > ) > > Is that right? If you want to add something else to complete the picture, > maybe it will be useful also for others. > The last two options are normally maintained, aren't they? Is there a > preferred one or I can freely choose the most convenient one? > > The second question is about *branches*. By reading the last messages in > this mailing list, I have understood that branches 3.2.x or 3.1.x are more > stable. Is that still like this? > > Thanks in advance for your help and suggestions. > Best regards, > > Chiara Sammarco > Technical Leader and Project Manager > > Via di Corticella, 315 | Bologna, BO 40128 > tel (+39) 06 24 19 585 | mobile (+39) 342 19 60 662 > www.geodatalab.it | management at geodatalab.it > > > *Nota di riservatezza: *Questa email contiene informazioni private e/o > confidenziali. Se hai ricevuto questo messaggio per errore sei pregato di > eliminarlo e notificare il mittente. Grazie per la collaborazione. > _______________________________________________ > geonode-devel mailing list > geonode-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geonode-devel > -- Rizky Maulana Nugraha Software Developer - Kartoza rizky at kartoza.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiara.sammarco at geodatalab.it Wed Apr 21 00:49:53 2021 From: chiara.sammarco at geodatalab.it (Chiara Sammarco) Date: Wed, 21 Apr 2021 09:49:53 +0200 Subject: [GeoNode-devel] Few questions about the current status (versions and branches) In-Reply-To: References: Message-ID: Hi, I just want to clarify that in my previous email, I was asking for confirmation. I don't know if a decision was made. I've read about the intention of doing that. I've read in the "GeoNode-user" mailing list an exchange started on the 7th of April (the email was titled "Geonode SPC") and G. Allegri replied that they were going to submit a proposal to remove SPC since nobody is maintaining it. My experience with GeoNode was with the SPC version (2.10rc). While I was working on some problems with HTTPS, I read an answer on that from A.Fabiani that said that the SPC version was not meant for production. So I thought maybe it was time to switch to another version. Regards, Chiara Sammarco Il 21/04/2021 06:53, Rizky Maulana Nugraha ha scritto: > Hi everyone, > > I'm interested to follow the discussion. > > > SpcGeonode is no longer maintained. > > I didn't realize about this: SPCGeoNode was no longer maintained. Was > this decision final? Will the recipes be excluded in the future from > GeoNode repo? > I've made some small patches into the scripts and docker-compose > recipes in the past because it's very easy to customize deployment > from those recipes. > I even made Kubernetes Helm charts recipes based on SPCGeoNode recipes > for our company, Kartoza. > > Was the reason SpcGeoNode no longer maintained because no one is > actively working inside that directory? > I've just realized that the SPCGeoNode section was no longer in the > main/master docs. > > Regards, > Rizky Maulana Nugraha > > On Tue, 20 Apr 2021 at 22:13, Chiara Sammarco > > > wrote: > > Hi all, > I have a few questions about the current status of GeoNode. > > The first question is about *geonode's installation versions*, as > far as I've understood: > > 1. SpcGeonode is no longer maintained. > 2. There's a new docker version (in the guide > ). > (About docker versions, I have noticed the geonode-project > repo. Which is > the difference?) > 3. It is possible?to follow a traditional installation (in the > guide - installation for Ubuntu 20.04lts > ) > > Is that right? If you want to add something else to complete the > picture, maybe it will be useful also for others. > The last two options are normally maintained, aren't they? Is > there a preferred one or I can freely choose the most convenient one? > > The second question is about *branches*. By reading the last > messages in this mailing list, I have understood?that branches > 3.2.x or 3.1.x are more stable. Is that still like this? > > Thanks in advance for your help and suggestions. > Best regards, > > Chiara Sammarco > Technical Leader and Project Manager > > Via di Corticella, 315 |?Bologna, BO 40128 > tel (+39) 06 24 19 585 |?mobile (+39) 342 19 60 662 > www.geodatalab.it | > management at geodatalab.it > > > > *Nota di riservatezza: *Questa email contiene informazioni private > e/o confidenziali. Se hai ricevuto questo messaggio per errore sei > pregato di eliminarlo e notificare il mittente. Grazie per la > collaborazione. > > _______________________________________________ > geonode-devel mailing list > geonode-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geonode-devel > > > > > -- > Rizky Maulana Nugraha > Software Developer - Kartoza > rizky at kartoza.com -- A presto, Chiara Sammarco GeoDataLab Via Tiburtina, 912 | Roma, RM 00156 www.geodatalab.it | management at geodatalab.it LinkedIn Twitter Facebook Nota di riservatezza: Questa email contiene informazioni private e/o confidenziali. Se hai ricevuto questo messaggio per errore sei pregato di eliminarlo e notificare il mittente. Grazie per la collaborazione. -- Questa e-mail ? stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From giovanni.allegri at geo-solutions.it Wed Apr 21 01:56:40 2021 From: giovanni.allegri at geo-solutions.it (G. Allegri) Date: Wed, 21 Apr 2021 10:56:40 +0200 Subject: [GeoNode-devel] Few questions about the current status (versions and branches) In-Reply-To: References: Message-ID: Dear Rizky, the decision to remove the SPC recipes has come along with the ongoing clean up work which is meant to remove stale / unmaintained code and scripts from GeoNode core. The official guides are targeted to the docker-compose that is officially shipped with GeoNode and the GeoNode project. As far as we can tell no other deployment recipe is receiving active maintenance, and probably nobody will provide support for them. Giovanni Il giorno mer 21 apr 2021 alle ore 09:57 Chiara Sammarco < chiara.sammarco at geodatalab.it> ha scritto: > Hi, > > I just want to clarify that in my previous email, I was asking for > confirmation. I don't know if a decision was made. I've read about the > intention of doing that. > > I've read in the "GeoNode-user" mailing list an exchange started on the > 7th of April (the email was titled "Geonode SPC") and G. Allegri replied > that they were going to submit a proposal to remove SPC since nobody is > maintaining it. > > My experience with GeoNode was with the SPC version (2.10rc). While I was > working on some problems with HTTPS, I read an answer on that from > A.Fabiani that said that the SPC version was not meant for production. So I > thought maybe it was time to switch to another version. > > Regards, > > Chiara Sammarco > Il 21/04/2021 06:53, Rizky Maulana Nugraha ha scritto: > > Hi everyone, > > I'm interested to follow the discussion. > > > SpcGeonode is no longer maintained. > > I didn't realize about this: SPCGeoNode was no longer maintained. Was this > decision final? Will the recipes be excluded in the future from GeoNode > repo? > I've made some small patches into the scripts and docker-compose recipes > in the past because it's very easy to customize deployment from those > recipes. > I even made Kubernetes Helm charts recipes based on SPCGeoNode recipes for > our company, Kartoza. > > Was the reason SpcGeoNode no longer maintained because no one is actively > working inside that directory? > I've just realized that the SPCGeoNode section was no longer in the > main/master docs. > > Regards, > Rizky Maulana Nugraha > > On Tue, 20 Apr 2021 at 22:13, Chiara Sammarco < > chiara.sammarco at geodatalab.it> wrote: > >> Hi all, >> I have a few questions about the current status of GeoNode. >> >> The first question is about *geonode's installation versions*, as far as >> I've understood: >> >> 1. SpcGeonode is no longer maintained. >> 2. There's a new docker version (in the guide >> ). >> (About docker versions, I have noticed the geonode-project >> repo. Which is the >> difference?) >> 3. It is possible to follow a traditional installation (in the guide >> - installation for Ubuntu 20.04lts >> >> ) >> >> Is that right? If you want to add something else to complete the picture, >> maybe it will be useful also for others. >> The last two options are normally maintained, aren't they? Is there a >> preferred one or I can freely choose the most convenient one? >> >> The second question is about *branches*. By reading the last messages in >> this mailing list, I have understood that branches 3.2.x or 3.1.x are more >> stable. Is that still like this? >> >> Thanks in advance for your help and suggestions. >> Best regards, >> >> Chiara Sammarco >> Technical Leader and Project Manager >> >> Via di Corticella, 315 | Bologna, BO 40128 >> tel (+39) 06 24 19 585 | mobile (+39) 342 19 60 662 >> www.geodatalab.it | management at geodatalab.it >> >> >> >> *Nota di riservatezza: *Questa email contiene informazioni private e/o >> confidenziali. Se hai ricevuto questo messaggio per errore sei pregato di >> eliminarlo e notificare il mittente. Grazie per la collaborazione. >> _______________________________________________ >> geonode-devel mailing list >> geonode-devel at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/geonode-devel >> > > > -- > Rizky Maulana Nugraha > Software Developer - Kartoza > rizky at kartoza.com > > -- > A presto, > Chiara Sammarco > > [image: GeoDataLab] > Via Tiburtina, 912 | Roma, RM 00156 > www.geodatalab.it | management at geodatalab.it > [image: LinkedIn] [image: > Twitter] [image: Facebook] > > Nota di riservatezza: Questa email contiene informazioni private e/o > confidenziali. Se hai ricevuto questo messaggio per errore sei pregato di > eliminarlo e notificare il mittente. Grazie per la collaborazione. > > > ------------------------------ > [image: Avast logo] > > Questa e-mail ? stata controllata per individuare virus con Avast > antivirus. > www.avast.com > > <#m_3247613046971251488_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > geonode-devel mailing list > geonode-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geonode-devel > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Giovanni Allegri Senior Project Manager GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mob.: +39 345 2815774 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From emilianocastaneda at spacesur.com Wed Apr 21 10:44:55 2021 From: emilianocastaneda at spacesur.com (=?UTF-8?Q?Emiliano_Casta=C3=B1eda?=) Date: Wed, 21 Apr 2021 19:44:55 +0200 Subject: [GeoNode-devel] Oauth Token created when pressing "genode" button on GeoServer login Message-ID: Hi to all We found that when trying to login to GeoServer 2.17.0 by pressing the GeoNode login button, it creates an Oauth Access Token with 10hs expiration time (the default of geonode-oauth-toolkit), not taking in account if there was an existing not expired one for the user (created by login to GeoNode with expiration time the value defined on settings.py). On the other side, When logging to GeoNode, if an existing valid token is available for the user, no new token is created. The first case seems like a bug to us. Can someone please confirm? Thanks! Emiliano -------------- next part -------------- An HTML attachment was scrubbed... URL: From alessio.fabiani at geo-solutions.it Thu Apr 22 00:21:21 2021 From: alessio.fabiani at geo-solutions.it (Alessio Fabiani) Date: Thu, 22 Apr 2021 09:21:21 +0200 Subject: [GeoNode-devel] Oauth Token created when pressing "genode" button on GeoServer login In-Reply-To: References: Message-ID: Hi Emiliano, thanks, I'll double check. Alessio. Il giorno gio 22 apr 2021 alle ore 09:14 Emiliano Casta?eda < emilianocastaneda at spacesur.com> ha scritto: > Hi to all > > We found that when trying to login to GeoServer 2.17.0 by pressing the > GeoNode login button, it creates an Oauth Access Token with 10hs > expiration time (the default of geonode-oauth-toolkit), not taking in > account if there was an existing not expired one for the user (created by > login to GeoNode with expiration time the value defined on settings.py). > > On the other side, When logging to GeoNode, if an existing valid token is > available for the user, no new token is created. > > The first case seems like a bug to us. > > Can someone please confirm? > > Thanks! > Emiliano > > _______________________________________________ > geonode-devel mailing list > geonode-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geonode-devel > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Alessio Fabiani @alfa7691 Founder/Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A - 55054 Massarosa (LU) - Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 331 6233686 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From emilianocastaneda at spacesur.com Thu Apr 22 01:39:22 2021 From: emilianocastaneda at spacesur.com (=?UTF-8?Q?Emiliano_Casta=C3=B1eda?=) Date: Thu, 22 Apr 2021 10:39:22 +0200 Subject: [GeoNode-devel] Oauth Token created when pressing "genode" button on GeoServer login In-Reply-To: References: Message-ID: Thanks Alessio! El jue, 22 abr 2021 a las 9:21, Alessio Fabiani (< alessio.fabiani at geo-solutions.it>) escribi?: > Hi Emiliano, > thanks, I'll double check. > > Alessio. > > Il giorno gio 22 apr 2021 alle ore 09:14 Emiliano Casta?eda < > emilianocastaneda at spacesur.com> ha scritto: > >> Hi to all >> >> We found that when trying to login to GeoServer 2.17.0 by pressing the >> GeoNode login button, it creates an Oauth Access Token with 10hs >> expiration time (the default of geonode-oauth-toolkit), not taking in >> account if there was an existing not expired one for the user (created by >> login to GeoNode with expiration time the value defined on settings.py). >> >> On the other side, When logging to GeoNode, if an existing valid token is >> available for the user, no new token is created. >> >> The first case seems like a bug to us. >> >> Can someone please confirm? >> >> Thanks! >> Emiliano >> >> _______________________________________________ >> geonode-devel mailing list >> geonode-devel at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/geonode-devel >> > > > -- > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > Ing. Alessio Fabiani > > @alfa7691 > Founder/Technical Lead > > > GeoSolutions S.A.S. > Via di Montramito 3/A - 55054 Massarosa (LU) - Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 331 6233686 > > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati ?GDPR?), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) ? un dato la cui conoscenza ? > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le ? giunto per errore, ? tenuta/o a cancellarlo, ogni altra > operazione ? illecita. Le sarei comunque grato se potesse darmene notizia. > > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 ?GDPR? - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > -- Emiliano Casta?eda VP Engineering +54 (11) 4342-2976/84 www.spacesur.com -------------- next part -------------- An HTML attachment was scrubbed... URL: