On Wed, Mar 28, 2012 at 19:40, Odhiambo Washington <odhiambo@gmail.com>wrote:

On Wed, Mar 28, 2012 at 19:13, Florian Fuchs <f@state-of-mind.de> wrote:

...

Hi Odhiambo,

...

Hey Jeff and all,

I followed the "five minute guide", but I am hitting a brickwall:

[root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup#

Am 28.03.12 17:13, schrieb Odhiambo Washington: python

...

manage.py syncdb Traceback (most recent call last): File "manage.py", line 29, in <module> execute_manager(settings) File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py",

...

line 459, in execute_manager utility.execute() File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py",

...

line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",

...

line 196, in run_from_argv self.execute(*args, **options.__dict__) File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",

...

line 232, in execute output = self.handle(*args, **options) File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py",

...

line 371, in handle return self.handle_noargs(**options) File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/commands/syncdb.py",

...

line 57, in handle_noargs cursor = connection.cursor() File

"/usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/dummy/base.py",

...

line 15, in complain raise ImproperlyConfigured("settings.DATABASES is improperly configured. " django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details.

You're doing nothing wrong! Except you're using the latest Django version (1.4) which was released only some days ago... :-)

In Django 1.2 support for multiple databases has been added, so they extended the format of the db definition in settings.py. It looks like in 1.4 the old format (which we have used so far) is no longer supported which most definitely causes the above error to be thrown.

Changing the DATABASE setting in dev_setup/settings.py should do the trick. Like here: https://docs.djangoproject.com/en/1.4/ref/settings/#databases

I will fix that in our launchpad branch as well, so these changes will go into the next alpha (which will probably be released not too far from now... :-)

Florian

One more thing:

In settings.py, I have this:

REST_SERVER = 'http://192.168.40.252:8001'

However, this doesn't seem to be respected when I do runserver:

[root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# python manage.py runserver Validating models...

0 errors found Django version 1.4, using settings 'dev_setup.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C.

[root@jaribu] /usr/home/wash# sockstat -l | grep 800 root python 77906 3 tcp4 127.0.0.1:8000 *:* root python 14108 43 tcp4 127.0.0.1:8001 *:*

Since I am not using the server as a Desktop, I need a way to access it remotely, not via 127.0.0.1

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223

I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.