[GeoNode-users] Custom Installation

Fri Feb 17 07:56:11 PST 2017

$ pip freeze | grep gsconfig
gsconfig==1.0.6
$ git rev-parse HEAD
fatal: Not a git repository (or any of the parent directories): .git

I get a zip file from github sugested on first reply (
https://github.com/GeoNode/geonode/tree/debian/2.6.0+alpha1), unziped and
copied content for my /home/geonode path.
What is the correct way to get .git from 2.6? Sorry, I'm newbie on this.

2017-02-17 13:44 GMT-02:00 Paolo Corti <pcorti at gmail.com>:

> That seems fine, though I don't see gsconfig being downgraded as it
> should according to Simone's suggestion.
>
> Could you check what is the output of: pip freeze | grep gsconfig
>
> Also please let me know what is the output of this: git rev-parse HEAD
>
> p
>
> On Fri, Feb 17, 2017 at 10:35 AM, Giovani Fronza
> <giovanifronza at gmail.com> wrote:
> > Wen run ($ sudo pip isntall -e .) returns a warning...
> >
> > Installing collected packages: GeoNode
> >   Running setup.py develop for GeoNode
> >
> >     warning: manifest_maker: MANIFEST.in, line 2: 'recursive-exclude'
> > expects <dir> <pattern1> <pattern2> ...
> >
> >     Creating /usr/local/lib/python2.7/dist-packages/GeoNode.egg-link
> (link
> > to .)
> >     GeoNode 2.5.16 is already the active version in easy-install.pth
> >
> >     Installed /home/geonode
> > Successfully installed GeoNode
> > Cleaning up...
> >
> >
> > 2017-02-17 13:19 GMT-02:00 Paolo Corti <pcorti at gmail.com>:
> >>
> >> Yes, after checking out the git tag, you should reinstall resources
> >> (with sudo pip install -e .) as there could be differences.
> >> p
> >>
> >> On Fri, Feb 17, 2017 at 10:09 AM, Simone Dalmasso
> >> <simone.dalmasso at gmail.com> wrote:
> >> > Hi, seems that you may have a wrong version of gsconfig. pls check
> that.
> >> >
> >> > 2017-02-17 16:05 GMT+01:00 Giovani Fronza <giovanifronza at gmail.com>:
> >> >>
> >> >> I think so. Don´t tried to start paver before, but now, it retuns
> this
> >> >> messanges:
> >> >> ...
> >> >> ---> pavement.start_django
> >> >> python manage.py runserver  &
> >> >> GeoNode is now available.
> >> >> root at vmgeo:/home/geonode# Performing system checks...
> >> >>
> >> >> System check identified some issues:
> >> >>
> >> >> WARNINGS:
> >> >> base.ResourceBase.tkeywords: (fields.W340) null has no effect on
> >> >> ManyToManyField.
> >> >>
> >> >> System check identified 1 issue (0 silenced).
> >> >> February 17, 2017 - 08:54:03
> >> >> Django version 1.8.17, using settings 'geonode.settings'
> >> >> Starting development server at http://127.0.0.1:8000/
> >> >> Quit the server with CONTROL-C.
> >> >>
> >> >>
> >> >> 2017-02-17 12:17 GMT-02:00 Paolo Corti <pcorti at gmail.com>:
> >> >>>
> >> >>> Before starting using httpd and mod_wsgi: does your GeoNode instance
> >> >>> work correctly with the development server? You can start it with
> >> >>> paver start, as suggested in the documentation page you have linked
> >> >>> p
> >> >>>
> >> >>> On Fri, Feb 17, 2017 at 8:31 AM, Giovani Fronza
> >> >>> <giovanifronza at gmail.com>
> >> >>> wrote:
> >> >>> > Thankyou very much Paolo!
> >> >>> >
> >> >>> > After installation I faced problem with wsgi. Something related to
> >> >>> > geoserver.catalog.
> >> >>> > I found this on apache error.log
> >> >>> >
> >> >>> >  mod_wsgi (pid=22240): Target WSGI script
> >> >>> > '/home/geonode/geonode/wsgi.py'
> >> >>> > cannot be loaded as Python module.
> >> >>> >  mod_wsgi (pid=22240): Exception occurred processing WSGI script
> >> >>> > '/home/geonode/geonode/wsgi.py'.
> >> >>> >  Traceback (most recent call last):
> >> >>> >    File "/home/geonode/geonode/wsgi.py", line 30, in <module>
> >> >>> >      application = get_wsgi_application()
> >> >>> >    File
> >> >>> > "/usr/local/lib/python2.7/dist-packages/django/core/wsgi.py",
> >> >>> > line
> >> >>> > 14, in get_wsgi_application
> >> >>> >      django.setup()
> >> >>> >    File "/usr/local/lib/python2.7/dist-packages/django/__init__.
> py",
> >> >>> > line
> >> >>> > 18, in setup
> >> >>> >      apps.populate(settings.INSTALLED_APPS)
> >> >>> >    File
> >> >>> > "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py",
> >> >>> > line 108, in populate
> >> >>> >      app_config.import_models(all_models)
> >> >>> >    File
> >> >>> > "/usr/local/lib/python2.7/dist-packages/django/apps/config.py",
> >> >>> > line
> >> >>> > 198, in import_models
> >> >>> >      self.models_module = import_module(models_module_name)
> >> >>> >    File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
> >> >>> > import_module
> >> >>> >      __import__(name)
> >> >>> >    File "/home/geonode/geonode/services/models.py", line 24, in
> >> >>> > <module>
> >> >>> >      from geoserver.catalog import FailedRequestError, Catalog
> >> >>> >  ImportError: No module named catalog
> >> >>> >
> >> >>> >
> >> >>> > How to resolv that?
> >> >>> >
> >> >>> > 2017-02-16 18:24 GMT-02:00 Paolo Corti <pcorti at gmail.com>:
> >> >>> >>
> >> >>> >> Hi Giovani
> >> >>> >> you should be able to get the 2.6 (note that it is still not
> >> >>> >> released)
> >> >>> >> by
> >> >>> >> checking out the 2.6 tag from git:
> >> >>> >> https://github.com/GeoNode/geonode/tree/debian/2.6.0+alpha1
> >> >>> >> hope it helps
> >> >>> >> p
> >> >>> >>
> >> >>> >> On Thu, Feb 16, 2017 at 3:09 PM, Giovani Fronza
> >> >>> >> <giovanifronza at gmail.com>
> >> >>> >> wrote:
> >> >>> >> > I've just installed the current geonode.git, according to the
> >> >>> >> > instructions
> >> >>> >> > presented on
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > http://docs.geonode.org/en/master/tutorials/admin/
> install/custom_install.html,
> >> >>> >> > and for my surprise that was installed the 2.7.dev version.
> >> >>> >> >
> >> >>> >> > I'm curious about 2.6 stable release. We have just started a
> big
> >> >>> >> > project
> >> >>> >> > to
> >> >>> >> > manage geospatial data and we would like to lead with a
> solution
> >> >>> >> > newest
> >> >>> >> > as
> >> >>> >> > possible.
> >> >>> >> >
> >> >>> >> > Is there a realistic date for 2.6 version launch?
> >> >>> >> >
> >> >>> >> > What are your recomendations for custom installation (for
> >> >>> >> > debian),
> >> >>> >> > considering this situation?
> >> >>> >> >
> >> >>> >> > Giovani
> >> >>> >> >
> >> >>> >> > _______________________________________________
> >> >>> >> > geonode-users mailing list
> >> >>> >> > geonode-users at lists.osgeo.org
> >> >>> >> > https://lists.osgeo.org/mailman/listinfo/geonode-users
> >> >>> >> >
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> >>> >> --
> >> >>> >> Paolo Corti
> >> >>> >> Geospatial software developer
> >> >>> >> web: http://www.paolocorti.net
> >> >>> >> twitter: @capooti
> >> >>> >> skype: capooti
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Paolo Corti
> >> >>> Geospatial software developer
> >> >>> web: http://www.paolocorti.net
> >> >>> twitter: @capooti
> >> >>> skype: capooti
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> geonode-users mailing list
> >> >> geonode-users at lists.osgeo.org
> >> >> https://lists.osgeo.org/mailman/listinfo/geonode-users
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Simone
> >>
> >>
> >>
> >> --
> >> Paolo Corti
> >> Geospatial software developer
> >> web: http://www.paolocorti.net
> >> twitter: @capooti
> >> skype: capooti
> >
> >
>
>
>
> --
> Paolo Corti
> Geospatial software developer
> web: http://www.paolocorti.net
> twitter: @capooti
> skype: capooti
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20170217/4f09c6c2/attachment.html>