[GeoNode-devel] Officially support Docker as a deployment method for production

[Alessio Fabiani]

+1 on root password security encryption
-1 on having a role service bounded to the local DB. We should really use
the standard REST based role service here.

Regards,

Alessio Fabiani

==
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

-------------------------------------------------------

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

2018-04-04 2:33 GMT+02:00 Olivier Dalang <olivier.dalang at gmail.com>:

> Dear all,
>
> Following some discussions that happened during the summit, I opened a
> GNIP about officially supporting Docker as a deployment strategy:
>
> https://github.com/GeoNode/geonode/issues/3707
>
> For convenience, I copied the content below.
>
> Following the procedure, please add your comments/+1s/-1s directly in the
> GNIP.
>
> Thank you in advance !
>
> Olivier Dalang
>
>
> GNIP :
>
> # Overview
>
> The idea of this GNIP is to officially support a production-grade
> deployment method using Docker. By production-grade, it is meant a
> deployment solution that satisfies basic needs in terms of performance and
> security.
>
> # Rationale
>
> 1. There's currently no clear deployment method supported for production
> (there's an entry about that in the doc, but it's incomplete and very hard
> to follow) which results on a lot of very poorly secured installations
> 2. Docker works on all major platforms (Windows, Linux, Mac OS X)
> 3. It's very easy to use (basically, start the whole stack in 1 command
> line, almost identical on any system)
> 4. It's very easy to make new releases (basically one git tag)
> 5. Similar setup for dev and production
> 6. It's possible to include features that are not strictly part of
> Geonode, but still essential for a production ready deployment (https
> encryption, backups...)
>
> Points 1. and 6. are a major problem for smaller institutions that don't
> have advanced sysadmins / security experts, which represents a lot of
> Geonode user (just look at the Geonode gallery and at how many of them use
> https).
>
> # Implementation
>
> I suggest an implementation similar to https://github.com/
> olivierdalang/SPCgeonode (as presented [earlier](https://lists.osgeo.
> org/pipermail/geonode-devel/2018-March/002108.html) on the ML)
>
> - Basically a Geonode-project (so that it's easy to customize, you can
> still get the vanilla geonode if you don't customize anything)
> - Including customized Dockerfile (such as Nginx, Geoserver, etc.)  in the
> same repo rather than in external repositories, so that releasing new
> versions can be done all in one place and that it's easier to know what's
> actually being installed
> - Including automatic ssl encryption and easy to configure backups using
> popular cloud provider
> - Optionally maintain a Rancher catalog entry (which is almost 0 work)
>
> I suggest mentioning that deployment method on the home page, making it
> clear that the apt-get method isn't production-ready out of the box.
>
> # Repository
>
> This could probably live in the Geonode-project repository.
>
>
>
>
>
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20180404/efdb6e4a/attachment.html>