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

[Benjamin Ducke]

On 11/05/16 13:51, Simone Dalmasso wrote:
> Sorry I don't understand which 'geonode' command are you referring to.
> If you refer to geonode syncdb from the geonode quick setup then you
> have to issue it before installing the theme.
>

I am talking about step 4 in the sequence
found here:

http://docs.geonode.org/en/master/tutorials/admin/customize_lookfeel/customize/setup_admin.html#setup-admin

This is what the official instructions tell
me to do:

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

As you can see: in step 4 I am supposed to run
the command 'geonode' without any arguments.
On a Ubuntu install from packages, this 'geonode'
script is located in '/usr/sbin', and when running
it without arguments, it will throw an error
message.

> after it you can still issue all the commands but using python manage.py.

Yes, that works fine.

Cheers,

Ben

> 
> 
> 
> 2016-05-11 13:37 GMT+02:00 Benjamin Ducke <benducke at fastmail.fm
> <mailto:benducke at fastmail.fm>>:
> 
>     Hi Simone --
> 
>     On 11/05/16 13:28, Simone Dalmasso wrote:
>     > Hi,
>     >
>     > yes those steps are for when you installed geonode using apt-get.
> 
>     Right, that's what I did.
> 
>     > They can be issued as they are
> 
>     But then 'geonode' will throw an error
>     message, as I described. I find that
>     a little disconcerting.
> 
>     > 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.
> 
>     So do I understand correctly, that I can just
>     skip running 'geonode'?
> 
>     Then maybe that step should be removed from
>     the instructions on the Web?
> 
>     Cheers and Thanks for your quick reply!
> 
>     Ben
> 
>     >
>     > 2016-05-11 12:57 GMT+02:00 Benjamin Ducke <benducke at fastmail.fm
>     <mailto:benducke at fastmail.fm>
>     > <mailto:benducke at fastmail.fm <mailto: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 <http://fastmail.fm> <http://fastmail.fm>
>     >> _______________________________________________
>     >> geonode-users mailing list
>     >> geonode-users at lists.osgeo.org
>     <mailto:geonode-users at lists.osgeo.org>
>     <mailto:geonode-users at lists.osgeo.org
>     <mailto:geonode-users at lists.osgeo.org>>
>     >> http://lists.osgeo.org/mailman/listinfo/geonode-users
>     >
>     >
>     >
>     >
>     > --
>     > Simone
> 
> 
> 
>     --
>     Dr. Benjamin Ducke
>     {*} Geospatial Consultant
>     {*} GIS Developer
> 
>     Spatial technology for the masses, not the classes:
>     experience free and open source GIS at http://gvsigce.org
>     _______________________________________________
>     geonode-users mailing list
>     geonode-users at lists.osgeo.org <mailto:geonode-users at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/geonode-users
> 
> 
> 
> 
> -- 
> Simone 



-- 
Dr. Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer

Spatial technology for the masses, not the classes:
experience free and open source GIS at http://gvsigce.org