[GeoNode-users] 'geonode' command on Ubuntu throws "Unknown command" when called without arguments

Simone Dalmasso simone.dalmasso at gmail.com
Wed May 11 04:28:52 PDT 2016


Hi,

yes those steps are for when you installed geonode using apt-get. They can
be issued as they are and the geonode theme will be installed systemwide as
geonode is and you need to have geonode installed before doing that.

You don't have to use django-admin except for the template creation. The
commands as they are using manage.py work fine. If you installed geonode
manually then it depends on your configuration but still is very similar.
The geonode command is not used anymore to do collectstatic because the
manage.py will take care of it.

2016-05-11 12:57 GMT+02:00 Benjamin Ducke <benducke at fastmail.fm>:
>
> Dear GeoNoders,
>
> I am currently setting up my first GeoNode installation, and trying to
> follow
> the official  documentation on customization and theming.
>
> I would appreciate some help/feedback with the 'geonode' command.
> My OS is Ubuntu 14.04 and I have installed GeoNode 2.4. from the
> official
> packages.
>
> On this page:
>
>
http://docs.geonode.org/en/master/tutorials/admin/customize_lookfeel/customize/setup_admin.html#setup-admin
>
> There is a sequence of commands that includes a call to 'geonode' (step
> 4):
>
> 1 $ cd /home/geonode/my_geonode
> 2 $ python manage.py collectstatic
> 3 $ python manage.py syncdb
> 4 $ /home/geonode/geonode
> 5 $ sudo pip install -e .
> 6 $ sudo service apache2 restart
>
> I am assuming that this refers to '/usr/sbin/geonode' when installed
> from
> the Ubuntu packages, correct? Said executable is a simple shell script
> wrapper for 'django-admin', which just determines whether to use
> 'django-admin' or 'django-admin.py' (right choice for my OS). So far so
> good. However, when just calling 'geonode' without any arguments, I get:
>
>   Unknown command: '--settings=geonode.settings'
>
> Apparently, this is because the arguments placeholder '$@' in
> '/usr/sbin/geonode'
> stays empty in this case, but 'django-admin.py' really wants to have the
> name
> of a subcommand.
>
> So my question is: Did 'django-admin.py' use to have a default
> subcommand in
> the past, but no longer? Or are the instructions on the web page above
> incomplete?
> Which django-admin subcommand should run in line 4 above?
>
> Many thanks for any pointers,
>
> Benjamin
>
> --
> Benjamin Ducke
> {*} Geospatial Consultant
> {*} GIS Developer
>
>   benducke AT fastmail.fm
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geonode-users




--
Simone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20160511/dda76725/attachment.html>


More information about the geonode-users mailing list