librelist archives

« back to archive

No createsuperuser for django-admin.py

No createsuperuser for django-admin.py

From:
Greg Corradini
Date:
2011-10-02 @ 17:30
Hello,
I'm following the instructions at
http://docs.geonode.org/1.1-RC1/getting-started.html for setting up a
GeoNode dev environment on Ubuntu 10.10. Is this the best and most
recent documentation on setting up GeoNode (it seems it is)?

Some problems I've run into that I would appreciate some help on:

1. There doesn't seem to be a createsuperuser command for
django-admin.py to run this statement:

             (geonode) $ django-admin.py createsuperuser
--settings=geonode.settings

Does it matter that I have a superuser if this command doesn't exist?


2. When I try to run Jetty with the folllowing command I get an error
stating "The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does
not exist or no valid version could be found":

            $ sh src/geoserver-geonode-ext/starup.sh


Any ideas?

Thanks

Re: [geonode] No createsuperuser for django-admin.py

From:
Joe Larson
Date:
2011-10-02 @ 17:36
did you try running `geonode createsuperuser` first?

~joe
On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:

> Hello,
> I'm following the instructions at
> http://docs.geonode.org/1.1-RC1/getting-started.html for setting up a
> GeoNode dev environment on Ubuntu 10.10. Is this the best and most
> recent documentation on setting up GeoNode (it seems it is)?
> 
> Some problems I've run into that I would appreciate some help on:
> 
> 1. There doesn't seem to be a createsuperuser command for
> django-admin.py to run this statement:
> 
>             (geonode) $ django-admin.py createsuperuser
> --settings=geonode.settings
> 
> Does it matter that I have a superuser if this command doesn't exist?
> 
> 
> 2. When I try to run Jetty with the folllowing command I get an error
> stating "The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does
> not exist or no valid version could be found":
> 
>            $ sh src/geoserver-geonode-ext/starup.sh
> 
> 
> Any ideas?
> 
> Thanks

Re: [geonode] No createsuperuser for django-admin.py

From:
Greg Corradini
Date:
2011-10-02 @ 21:24
yep, i've tried using the command '$ geonode createsuperuser' both in venv
and outside...

both return 'geonode command not found'

-mobile I/O, forgive mistakes

On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:

did you try running `geonode createsuperuser` first?

~joe

On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:

> Hello,
> I'm following the instructions at
> h...

Re: [geonode] No createsuperuser for django-admin.py

From:
David Winslow
Date:
2011-10-03 @ 12:50
What's the error message that you get?

Also, do you have django installed in the system-wide site packages
directory?  If so the django-admin script may be on your PATH ahead of the
one installed in GeoNode (or GeoNode might not have bothered to install one,
I forget.) The system-wide script won't see packages installed in the
virtualenv (which is basically the point of virtualenv.)

You can check with "which django-admin.py"; that works inside or outside the
virtualenv.

If you don't have django installed in the virtualenv, you can install it
with "pip -U django==1.2.0" (make sure to activate the virtualenv first)
If you have Django installed twice and the wrong one is being used, you can
specify the full path to the script, like <venv>/bin/django-admin.py

It might be something different so please let us know if that helps.

--
David Winslow
OpenGeo - http://opengeo.org/

On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini <gregcorradini@gmail.com>wrote:

> yep, i've tried using the command '$ geonode createsuperuser' both in venv
> and outside...
>
> both return 'geonode command not found'
>
> -mobile I/O, forgive mistakes
>
> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
>
> did you try running `geonode createsuperuser` first?
>
> ~joe
>
> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
>
> > Hello,
> > I'm following the instructions at
> > h...
>
>

Re: [geonode] No createsuperuser for django-admin.py

From:
Greg Corradini
Date:
2011-10-03 @ 14:14
Hey David,
I've tried the things you recommend but I'm still getting the error
"Unknown command 'createsuperuser' ". I'm wondering if I should try
using the GeoNode packages that I've seen talked about on this mailing
list as a optional install.

Here's the details on my GeoNode install:

root@mochi:/home/GIT/geonode# source bin/activate

(geonode)root@mochi:/home/GIT/geonode# which django-admin.py
/home/GIT/geonode/bin/django-admin.py

(geonode)root@mochi:/home/GIT/geonode# pip install django==1.2.0
Requirement already satisfied (use --upgrade to upgrade):
django==1.2.0 in ./lib/python2.6/site-packages

(geonode)root@mochi:/home/GIT/geonode# django-admin.py
...

Type 'django-admin.py help <subcommand>' for help on a specific subcommand.

Available subcommands:
  cleanup
  compilemessages
  createcachetable
  dbshell
  diffsettings
  dumpdata
  flush
...

Thanks
Greg

On Mon, Oct 3, 2011 at 5:50 AM, David Winslow <dwinslow@opengeo.org> wrote:
> What's the error message that you get?
> Also, do you have django installed in the system-wide site packages
> directory?  If so the django-admin script may be on your PATH ahead of the
> one installed in GeoNode (or GeoNode might not have bothered to install one,
> I forget.) The system-wide script won't see packages installed in the
> virtualenv (which is basically the point of virtualenv.)
> You can check with "which django-admin.py"; that works inside or outside the
> virtualenv.
> If you don't have django installed in the virtualenv, you can install it
> with "pip -U django==1.2.0" (make sure to activate the virtualenv first)
> If you have Django installed twice and the wrong one is being used, you can
> specify the full path to the script, like <venv>/bin/django-admin.py
> It might be something different so please let us know if that helps.
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini <gregcorradini@gmail.com>
> wrote:
>>
>> yep, i've tried using the command '$ geonode createsuperuser' both in venv
>> and outside...
>>
>> both return 'geonode command not found'
>>
>> -mobile I/O, forgive mistakes
>>
>> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
>>
>> did you try running `geonode createsuperuser` first?
>>
>> ~joe
>>
>> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
>>
>> > Hello,
>> > I'm following the instructions at
>> > h...
>



-- 
Greg

Re: [geonode] No createsuperuser for django-admin.py

From:
David Winslow
Date:
2011-10-03 @ 18:38
Without the '--settings=geonode.settings' the "django-admin.py help" command
will not list many commands.  'createsuperuser' is one of the ones that
won't show up.

--
David Winslow
OpenGeo - http://opengeo.org/

On Mon, Oct 3, 2011 at 10:14 AM, Greg Corradini <gregcorradini@gmail.com>wrote:

> Hey David,
> I've tried the things you recommend but I'm still getting the error
> "Unknown command 'createsuperuser' ". I'm wondering if I should try
> using the GeoNode packages that I've seen talked about on this mailing
> list as a optional install.
>
> Here's the details on my GeoNode install:
>
> root@mochi:/home/GIT/geonode# source bin/activate
>
> (geonode)root@mochi:/home/GIT/geonode# which django-admin.py
> /home/GIT/geonode/bin/django-admin.py
>
> (geonode)root@mochi:/home/GIT/geonode# pip install django==1.2.0
> Requirement already satisfied (use --upgrade to upgrade):
> django==1.2.0 in ./lib/python2.6/site-packages
>
> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
> ...
>
> Type 'django-admin.py help <subcommand>' for help on a specific subcommand.
>
> Available subcommands:
>  cleanup
>  compilemessages
>  createcachetable
>  dbshell
>  diffsettings
>  dumpdata
>  flush
> ...
>
> Thanks
> Greg
>
> On Mon, Oct 3, 2011 at 5:50 AM, David Winslow <dwinslow@opengeo.org>
> wrote:
> > What's the error message that you get?
> > Also, do you have django installed in the system-wide site packages
> > directory?  If so the django-admin script may be on your PATH ahead of
> the
> > one installed in GeoNode (or GeoNode might not have bothered to install
> one,
> > I forget.) The system-wide script won't see packages installed in the
> > virtualenv (which is basically the point of virtualenv.)
> > You can check with "which django-admin.py"; that works inside or outside
> the
> > virtualenv.
> > If you don't have django installed in the virtualenv, you can install it
> > with "pip -U django==1.2.0" (make sure to activate the virtualenv first)
> > If you have Django installed twice and the wrong one is being used, you
> can
> > specify the full path to the script, like <venv>/bin/django-admin.py
> > It might be something different so please let us know if that helps.
> > --
> > David Winslow
> > OpenGeo - http://opengeo.org/
> > On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini <gregcorradini@gmail.com>
> > wrote:
> >>
> >> yep, i've tried using the command '$ geonode createsuperuser' both in
> venv
> >> and outside...
> >>
> >> both return 'geonode command not found'
> >>
> >> -mobile I/O, forgive mistakes
> >>
> >> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
> >>
> >> did you try running `geonode createsuperuser` first?
> >>
> >> ~joe
> >>
> >> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
> >>
> >> > Hello,
> >> > I'm following the instructions at
> >> > h...
> >
>
>
>
> --
> Greg
>

Re: [geonode] No createsuperuser for django-admin.py

From:
Greg Corradini
Date:
2011-10-03 @ 19:01
Hey David,
Thanks for your help. I'm sure I don't have Django installed anywhere
else on my system. As for the "django-admin.py help" issue, i've tried
the following options with no luck:

(geonode)root@mochi:/home/GIT/geonode# django-admin.py
--settings=geonode.settings help
Unknown command: '--settings=geonode.settings'
Type 'django-admin.py help' for usage.
(geonode)root@mochi:/home/GIT/geonode# django-admin.py
--settings=geonode.settings
Unknown command: '--settings=geonode.settings'
Type 'django-admin.py help' for usage.
(geonode)root@mochi:/home/GIT/geonode# django-admin.py help
--settings=geonode.settings
Usage: django-admin.py subcommand [options] [args]

Options:
  -v VERBOSITY, --verbosity=VERBOSITY
                        Verbosity level; 0=minimal output, 1=normal output,
                        2=all output
  --settings=SETTINGS   The Python path to a settings module, e.g.
                        "myproject.settings.main". If this isn't provided, the
                        DJANGO_SETTINGS_MODULE environment variable will be
                        used.
  --pythonpath=PYTHONPATH
                        A directory to add to the Python path, e.g.
                        "/home/djangoprojects/myproject".
  --traceback           Print traceback on exception
  --version             show program's version number and exit
  -h, --help            show this help message and exit

Type 'django-admin.py help <subcommand>' for help on a specific subcommand.

Available subcommands:
  cleanup
  compilemessages
  createcachetable
  dbshell
  diffsettings
  dumpdata
  flush
  inspectdb
  loaddata
  makemessages
  reset
  runfcgi
  runserver
  shell
  sql
  sqlall
  sqlclear
  sqlcustom
  sqlflush
  sqlindexes
  sqlinitialdata
  sqlreset
  sqlsequencereset
  startapp
  startproject
  syncdb
  test
  testserver
  validate
(geonode)root@mochi:/home/GIT/geonode#




On Mon, Oct 3, 2011 at 11:38 AM, David Winslow <dwinslow@opengeo.org> wrote:
> Without the '--settings=geonode.settings' the "django-admin.py help" command
> will not list many commands.  'createsuperuser' is one of the ones that
> won't show up.
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
> On Mon, Oct 3, 2011 at 10:14 AM, Greg Corradini <gregcorradini@gmail.com>
> wrote:
>>
>> Hey David,
>> I've tried the things you recommend but I'm still getting the error
>> "Unknown command 'createsuperuser' ". I'm wondering if I should try
>> using the GeoNode packages that I've seen talked about on this mailing
>> list as a optional install.
>>
>> Here's the details on my GeoNode install:
>>
>> root@mochi:/home/GIT/geonode# source bin/activate
>>
>> (geonode)root@mochi:/home/GIT/geonode# which django-admin.py
>> /home/GIT/geonode/bin/django-admin.py
>>
>> (geonode)root@mochi:/home/GIT/geonode# pip install django==1.2.0
>> Requirement already satisfied (use --upgrade to upgrade):
>> django==1.2.0 in ./lib/python2.6/site-packages
>>
>> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
>> ...
>>
>> Type 'django-admin.py help <subcommand>' for help on a specific
>> subcommand.
>>
>> Available subcommands:
>>  cleanup
>>  compilemessages
>>  createcachetable
>>  dbshell
>>  diffsettings
>>  dumpdata
>>  flush
>> ...
>>
>> Thanks
>> Greg
>>
>> On Mon, Oct 3, 2011 at 5:50 AM, David Winslow <dwinslow@opengeo.org>
>> wrote:
>> > What's the error message that you get?
>> > Also, do you have django installed in the system-wide site packages
>> > directory?  If so the django-admin script may be on your PATH ahead of
>> > the
>> > one installed in GeoNode (or GeoNode might not have bothered to install
>> > one,
>> > I forget.) The system-wide script won't see packages installed in the
>> > virtualenv (which is basically the point of virtualenv.)
>> > You can check with "which django-admin.py"; that works inside or outside
>> > the
>> > virtualenv.
>> > If you don't have django installed in the virtualenv, you can install it
>> > with "pip -U django==1.2.0" (make sure to activate the virtualenv first)
>> > If you have Django installed twice and the wrong one is being used, you
>> > can
>> > specify the full path to the script, like <venv>/bin/django-admin.py
>> > It might be something different so please let us know if that helps.
>> > --
>> > David Winslow
>> > OpenGeo - http://opengeo.org/
>> > On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini <gregcorradini@gmail.com>
>> > wrote:
>> >>
>> >> yep, i've tried using the command '$ geonode createsuperuser' both in
>> >> venv
>> >> and outside...
>> >>
>> >> both return 'geonode command not found'
>> >>
>> >> -mobile I/O, forgive mistakes
>> >>
>> >> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
>> >>
>> >> did you try running `geonode createsuperuser` first?
>> >>
>> >> ~joe
>> >>
>> >> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
>> >>
>> >> > Hello,
>> >> > I'm following the instructions at
>> >> > h...
>> >
>>
>>
>>
>> --
>> Greg
>
>



-- 
Greg

Re: [geonode] No createsuperuser for django-admin.py

From:
David Winslow
Date:
2011-10-03 @ 19:07
Were there any error messages printed during the setup steps?  I know
there's a lot of output but I imagine it would be near the end of the build
process.

--
David Winslow
OpenGeo - http://opengeo.org/

On Mon, Oct 3, 2011 at 3:01 PM, Greg Corradini <gregcorradini@gmail.com>wrote:

> Hey David,
> Thanks for your help. I'm sure I don't have Django installed anywhere
> else on my system. As for the "django-admin.py help" issue, i've tried
> the following options with no luck:
>
> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
> --settings=geonode.settings help
> Unknown command: '--settings=geonode.settings'
> Type 'django-admin.py help' for usage.
> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
> --settings=geonode.settings
> Unknown command: '--settings=geonode.settings'
> Type 'django-admin.py help' for usage.
> (geonode)root@mochi:/home/GIT/geonode# django-admin.py help
> --settings=geonode.settings
> Usage: django-admin.py subcommand [options] [args]
>
> Options:
>  -v VERBOSITY, --verbosity=VERBOSITY
>                        Verbosity level; 0=minimal output, 1=normal output,
>                        2=all output
>  --settings=SETTINGS   The Python path to a settings module, e.g.
>                        "myproject.settings.main". If this isn't provided,
> the
>                        DJANGO_SETTINGS_MODULE environment variable will be
>                        used.
>  --pythonpath=PYTHONPATH
>                        A directory to add to the Python path, e.g.
>                        "/home/djangoprojects/myproject".
>  --traceback           Print traceback on exception
>  --version             show program's version number and exit
>  -h, --help            show this help message and exit
>
> Type 'django-admin.py help <subcommand>' for help on a specific subcommand.
>
> Available subcommands:
>  cleanup
>  compilemessages
>  createcachetable
>  dbshell
>  diffsettings
>  dumpdata
>  flush
>   inspectdb
>  loaddata
>  makemessages
>  reset
>  runfcgi
>  runserver
>  shell
>  sql
>  sqlall
>  sqlclear
>  sqlcustom
>  sqlflush
>  sqlindexes
>  sqlinitialdata
>  sqlreset
>  sqlsequencereset
>  startapp
>  startproject
>  syncdb
>  test
>  testserver
>  validate
> (geonode)root@mochi:/home/GIT/geonode#
>
>
>
>
> On Mon, Oct 3, 2011 at 11:38 AM, David Winslow <dwinslow@opengeo.org>
> wrote:
> > Without the '--settings=geonode.settings' the "django-admin.py help"
> command
> > will not list many commands.  'createsuperuser' is one of the ones that
> > won't show up.
> > --
> > David Winslow
> > OpenGeo - http://opengeo.org/
> >
> > On Mon, Oct 3, 2011 at 10:14 AM, Greg Corradini <gregcorradini@gmail.com
> >
> > wrote:
> >>
> >> Hey David,
> >> I've tried the things you recommend but I'm still getting the error
> >> "Unknown command 'createsuperuser' ". I'm wondering if I should try
> >> using the GeoNode packages that I've seen talked about on this mailing
> >> list as a optional install.
> >>
> >> Here's the details on my GeoNode install:
> >>
> >> root@mochi:/home/GIT/geonode# source bin/activate
> >>
> >> (geonode)root@mochi:/home/GIT/geonode# which django-admin.py
> >> /home/GIT/geonode/bin/django-admin.py
> >>
> >> (geonode)root@mochi:/home/GIT/geonode# pip install django==1.2.0
> >> Requirement already satisfied (use --upgrade to upgrade):
> >> django==1.2.0 in ./lib/python2.6/site-packages
> >>
> >> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
> >> ...
> >>
> >> Type 'django-admin.py help <subcommand>' for help on a specific
> >> subcommand.
> >>
> >> Available subcommands:
> >>  cleanup
> >>  compilemessages
> >>  createcachetable
> >>  dbshell
> >>  diffsettings
> >>  dumpdata
> >>  flush
> >> ...
> >>
> >> Thanks
> >> Greg
> >>
> >> On Mon, Oct 3, 2011 at 5:50 AM, David Winslow <dwinslow@opengeo.org>
> >> wrote:
> >> > What's the error message that you get?
> >> > Also, do you have django installed in the system-wide site packages
> >> > directory?  If so the django-admin script may be on your PATH ahead of
> >> > the
> >> > one installed in GeoNode (or GeoNode might not have bothered to
> install
> >> > one,
> >> > I forget.) The system-wide script won't see packages installed in the
> >> > virtualenv (which is basically the point of virtualenv.)
> >> > You can check with "which django-admin.py"; that works inside or
> outside
> >> > the
> >> > virtualenv.
> >> > If you don't have django installed in the virtualenv, you can install
> it
> >> > with "pip -U django==1.2.0" (make sure to activate the virtualenv
> first)
> >> > If you have Django installed twice and the wrong one is being used,
> you
> >> > can
> >> > specify the full path to the script, like <venv>/bin/django-admin.py
> >> > It might be something different so please let us know if that helps.
> >> > --
> >> > David Winslow
> >> > OpenGeo - http://opengeo.org/
> >> > On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini <
> gregcorradini@gmail.com>
> >> > wrote:
> >> >>
> >> >> yep, i've tried using the command '$ geonode createsuperuser' both in
> >> >> venv
> >> >> and outside...
> >> >>
> >> >> both return 'geonode command not found'
> >> >>
> >> >> -mobile I/O, forgive mistakes
> >> >>
> >> >> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
> >> >>
> >> >> did you try running `geonode createsuperuser` first?
> >> >>
> >> >> ~joe
> >> >>
> >> >> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
> >> >>
> >> >> > Hello,
> >> >> > I'm following the instructions at
> >> >> > h...
> >> >
> >>
> >>
> >>
> >> --
> >> Greg
> >
> >
>
>
>
> --
> Greg
>

Re: [geonode] No createsuperuser for django-admin.py

From:
Greg Corradini
Date:
2011-10-03 @ 19:31
David,
No, I don't see any outstanding build errors related to Python. I only
see build warnings related to comments and incompatible implicit
declarations. Sorry, wish I could help more. If you have any more
ideas feel free to holler.

Thanks
Greg

On Mon, Oct 3, 2011 at 12:07 PM, David Winslow <dwinslow@opengeo.org> wrote:
> Were there any error messages printed during the setup steps?  I know
> there's a lot of output but I imagine it would be near the end of the build
> process.
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
> On Mon, Oct 3, 2011 at 3:01 PM, Greg Corradini <gregcorradini@gmail.com>
> wrote:
>>
>> Hey David,
>> Thanks for your help. I'm sure I don't have Django installed anywhere
>> else on my system. As for the "django-admin.py help" issue, i've tried
>> the following options with no luck:
>>
>> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
>> --settings=geonode.settings help
>> Unknown command: '--settings=geonode.settings'
>> Type 'django-admin.py help' for usage.
>> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
>> --settings=geonode.settings
>> Unknown command: '--settings=geonode.settings'
>> Type 'django-admin.py help' for usage.
>> (geonode)root@mochi:/home/GIT/geonode# django-admin.py help
>> --settings=geonode.settings
>> Usage: django-admin.py subcommand [options] [args]
>>
>> Options:
>>  -v VERBOSITY, --verbosity=VERBOSITY
>>                        Verbosity level; 0=minimal output, 1=normal output,
>>                        2=all output
>>  --settings=SETTINGS   The Python path to a settings module, e.g.
>>                        "myproject.settings.main". If this isn't provided,
>> the
>>                        DJANGO_SETTINGS_MODULE environment variable will be
>>                        used.
>>  --pythonpath=PYTHONPATH
>>                        A directory to add to the Python path, e.g.
>>                        "/home/djangoprojects/myproject".
>>  --traceback           Print traceback on exception
>>  --version             show program's version number and exit
>>  -h, --help            show this help message and exit
>>
>> Type 'django-admin.py help <subcommand>' for help on a specific
>> subcommand.
>>
>> Available subcommands:
>>  cleanup
>>  compilemessages
>>  createcachetable
>>  dbshell
>>  diffsettings
>>  dumpdata
>>  flush
>>  inspectdb
>>  loaddata
>>  makemessages
>>  reset
>>  runfcgi
>>  runserver
>>  shell
>>  sql
>>  sqlall
>>  sqlclear
>>  sqlcustom
>>  sqlflush
>>  sqlindexes
>>  sqlinitialdata
>>  sqlreset
>>  sqlsequencereset
>>  startapp
>>  startproject
>>  syncdb
>>  test
>>  testserver
>>  validate
>> (geonode)root@mochi:/home/GIT/geonode#
>>
>>
>>
>>
>> On Mon, Oct 3, 2011 at 11:38 AM, David Winslow <dwinslow@opengeo.org>
>> wrote:
>> > Without the '--settings=geonode.settings' the "django-admin.py help"
>> > command
>> > will not list many commands.  'createsuperuser' is one of the ones that
>> > won't show up.
>> > --
>> > David Winslow
>> > OpenGeo - http://opengeo.org/
>> >
>> > On Mon, Oct 3, 2011 at 10:14 AM, Greg Corradini
>> > <gregcorradini@gmail.com>
>> > wrote:
>> >>
>> >> Hey David,
>> >> I've tried the things you recommend but I'm still getting the error
>> >> "Unknown command 'createsuperuser' ". I'm wondering if I should try
>> >> using the GeoNode packages that I've seen talked about on this mailing
>> >> list as a optional install.
>> >>
>> >> Here's the details on my GeoNode install:
>> >>
>> >> root@mochi:/home/GIT/geonode# source bin/activate
>> >>
>> >> (geonode)root@mochi:/home/GIT/geonode# which django-admin.py
>> >> /home/GIT/geonode/bin/django-admin.py
>> >>
>> >> (geonode)root@mochi:/home/GIT/geonode# pip install django==1.2.0
>> >> Requirement already satisfied (use --upgrade to upgrade):
>> >> django==1.2.0 in ./lib/python2.6/site-packages
>> >>
>> >> (geonode)root@mochi:/home/GIT/geonode# django-admin.py
>> >> ...
>> >>
>> >> Type 'django-admin.py help <subcommand>' for help on a specific
>> >> subcommand.
>> >>
>> >> Available subcommands:
>> >>  cleanup
>> >>  compilemessages
>> >>  createcachetable
>> >>  dbshell
>> >>  diffsettings
>> >>  dumpdata
>> >>  flush
>> >> ...
>> >>
>> >> Thanks
>> >> Greg
>> >>
>> >> On Mon, Oct 3, 2011 at 5:50 AM, David Winslow <dwinslow@opengeo.org>
>> >> wrote:
>> >> > What's the error message that you get?
>> >> > Also, do you have django installed in the system-wide site packages
>> >> > directory?  If so the django-admin script may be on your PATH ahead
>> >> > of
>> >> > the
>> >> > one installed in GeoNode (or GeoNode might not have bothered to
>> >> > install
>> >> > one,
>> >> > I forget.) The system-wide script won't see packages installed in the
>> >> > virtualenv (which is basically the point of virtualenv.)
>> >> > You can check with "which django-admin.py"; that works inside or
>> >> > outside
>> >> > the
>> >> > virtualenv.
>> >> > If you don't have django installed in the virtualenv, you can install
>> >> > it
>> >> > with "pip -U django==1.2.0" (make sure to activate the virtualenv
>> >> > first)
>> >> > If you have Django installed twice and the wrong one is being used,
>> >> > you
>> >> > can
>> >> > specify the full path to the script, like <venv>/bin/django-admin.py
>> >> > It might be something different so please let us know if that helps.
>> >> > --
>> >> > David Winslow
>> >> > OpenGeo - http://opengeo.org/
>> >> > On Sun, Oct 2, 2011 at 5:24 PM, Greg Corradini
>> >> > <gregcorradini@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> yep, i've tried using the command '$ geonode createsuperuser' both
>> >> >> in
>> >> >> venv
>> >> >> and outside...
>> >> >>
>> >> >> both return 'geonode command not found'
>> >> >>
>> >> >> -mobile I/O, forgive mistakes
>> >> >>
>> >> >> On Oct 2, 2011 10:36 AM, "Joe Larson" <joelarso@gmail.com> wrote:
>> >> >>
>> >> >> did you try running `geonode createsuperuser` first?
>> >> >>
>> >> >> ~joe
>> >> >>
>> >> >> On Oct 2, 2011, at 10:30 AM, Greg Corradini wrote:
>> >> >>
>> >> >> > Hello,
>> >> >> > I'm following the instructions at
>> >> >> > h...
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Greg
>> >
>> >
>>
>>
>>
>> --
>> Greg
>
>



-- 
Greg