<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Dear Jose,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><div class="">To update to Master, Do I need another machine or it can be done on the same server? The problem is I just have the one server to get it done, and is not particular powerful (2 cores, 4GB memory, 60GB on disk).</div></div></blockquote></div></blockquote></div><div class=""><br class=""></div><div class="">I understand your problem with having only one server. For every option I can think of this</div><div class="">guide from Oliver should give you an idea of what to backup first and how:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/olivierdalang/SPCgeonode#how-to-migrate-from-an-existing-standard-geonode-install" class="">https://github.com/olivierdalang/SPCgeonode#how-to-migrate-from-an-existing-standard-geonode-install</a></div><div class=""><br class=""></div><div class=""># # # # # # # # #</div><div class=""><br class=""></div><div class=""><b class="">A) Backup -> test locally -> reset your VM -> import / migrate all data live again</b></div><div class=""><br class=""></div><div class="">This might be one of the cleanest but also work intense solutions. </div><div class=""><br class=""></div><div class=""> - Backup your live data</div><div class=""> - Test the installation/migration locally (you could use vagrant for spinning an Ubuntu instance in seconds)</div><div class=""> - Create a snapshot of your live VM (!!!)</div><div class=""> - Reset your live instance to a fresh state</div><div class=""> - Repeat the install with your production VM and migrate/import your data as you did locally.</div><div class=""><br class=""></div><div class=""><b class="">B) Use GeoServer and Postgresql install from apt -> manually install the core.</b></div><div class=""><br class=""></div><div class="">Again a snapshot gives you safety. Don´t miss to make use of it if you can! </div><div class=""><br class=""></div><div class=""> - Clone geonode-project master branch <a href="https://github.com/GeoNode/geonode-project" class="">https://github.com/GeoNode/geonode-project</a></div><div class=""> - Follow the README to create a virtualenv which will isolate python packages from globally installed by apt</div><div class=""> - Enable the geoserver boilerplate settings file <a href="https://github.com/GeoNode/geonode-project/blob/master/project_name/local_settings.py.sample" class="">https://github.com/GeoNode/geonode-project/blob/master/project_name/local_settings.py.sample</a> </div><div class=""> and add your credentials/path for PostgreSQL and geoserver. </div><div class=""> - Update Apache conf that it´s pointing to your new Geonode install (backup the conf file!)</div><div class=""> - Migrate your database as mentioned in Olivier's readme and if needed upgrade geoserver to a newer version.</div><div class=""><br class=""></div><div class=""><b class="">C) Install geonode docker -> and migrate your apt setup</b></div><div class=""><br class=""></div><div class="">This might be the most secure solution as you can always easily uninstall docker again and restart your</div><div class="">stack. Be prepared that docker install might need some more knowledge regarding its configuration. </div><div class=""><br class=""></div><div class=""> - Backup all your data, </div><div class=""> - Shut down the current Postgres, Geoserver, Apache, etc setup</div><div class=""> - Install the docker stack</div><div class=""> - Migrate your data and continue using docker</div><div class=""><br class=""></div><div class="">Find here a good writeup where to start with docker:</div><div class=""><a href="https://docs.google.com/document/d/1S0ac9IR9IW9tUjMu7JETPLUjnfQ6P87m1PKNko8IPWY" class="">https://docs.google.com/document/d/1S0ac9IR9IW9tUjMu7JETPLUjnfQ6P87m1PKNko8IPWY</a></div><div class="">(credits: <a href="https://geo-solutions.it" class="">https://geo-solutions.it</a>)</div><div class=""><br class=""></div><div class=""># # # # # # # # #</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr" class=""><div class=""> I try once before following the instructions provided here <a href="https://docs.google.com/document/d/1jNg2BKn2H9Haoyqpe7XkK_Nj-siL7PUlhP40hGi9OZ8/edit" target="_blank" class="">https://docs.google.com/document/d/1jNg2BKn2H9Haoyqpe7XkK_Nj-siL7PUlhP40hGi9OZ8/edit</a> for Ubuntu 18.04, but I don't know if this update can be done in Ubuntu 16.04 as well.</div></div></blockquote></div></blockquote></div><div class=""><br class=""></div><div class="">For all options you could use Ubuntu Bionic or Xenial. </div><div class="">With A) and B) the install differs a bit (different package Versions) but the migration steps are the same.</div><div class=""><br class=""></div><div class="">If you´re familiar with Docker and your server resources suffice I would suggest Option C.</div><div class="">If you new to Docker at all I would go with B)</div><div class="">( A) would be the last I would do )</div><div class=""><br class=""></div><div class="">These are all just rough ideas which might need fine tuning here and there but I hope</div><div class="">you get the ideas. If you need more insights don´t hesitate to ask.</div><div class="">And, </div><div class=""> ⚠️ don´t forget backups, backups, backups ;)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Toni</div><div class=""><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">Am 31.03.2019 um 15:08 schrieb Jose Cáceres <<a href="mailto:jose.atyus@gmail.com" class="">jose.atyus@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/c3d427f79342a163f3b52134a9f6f4dffc7a89e9.png?u=16998">Hi,<div class=""><br class=""></div><div class="">One more thing I forgot to mention, I don't know if is relevant, if I load any layers on the geoexplorer client on /maps/new, it does show the extent of the layers automatically as I load them, the problem is just on the preview of the layer on the /layers/layer_name page.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class=""><br class=""></div><div class="">José<br class=""><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>