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 <[email protected]> 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 <[email protected]>
> 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 <[email protected]>
>> 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 <[email protected]>
>> > 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" <[email protected]> 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
