Re: [mezzanine-users] Getting started - error with createdb

[Brian Schott]

Are you doing the tutorial site or trying to integrate into your existing site?  That command is in mezzanine.core.management.commands, so are you sure that mezzanine.core is in INSTALLED_APPS? 

-------------------------------------------------

Brian Schott, CTO

Nimbis Services, Inc.

brian....@nimbisservices.com

ph: 443-274-6064  fx: 443-274-6060

On Aug 14, 2012, at 4:38 PM, Doug Evenhouse <do...@evenhouseconsulting.com> wrote:

I'm just getting started with Mezzanine - hoping to replace my home-grown CMS (also built with Django) - and am having trouble out of the gate.

I've created a new virtualenv for Mezzanine and followed the quick steps as given on the Mezzanine home page. However, when I attempt to create the database an "Unknown command" error is thrown:

Unknown command: 'createdb'

I've not done anything to configure a database assuming a sqlite database would be created by default.

Have I assumed too much? What am I missing?

-Doug

[Stephen McDonald]

The error indicates Django can't find the management command.

Are you able to import it from the Django shell?

$ ./manage.py shell      

Python 2.7.1 (r271:86832, Jul 31 2011, 19:30:53) 

[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

(InteractiveConsole)

>>> from mezzanine.core.management.commands.createdb import Command

>>>

On Wed, Aug 15, 2012 at 7:07 AM, Doug Evenhouse <do...@evenhouseconsulting.com> wrote:

I'm just following the "quick start" instructions on the Mezzanine home page. The default settings.py of the project created by "mezzanine-project myproject" appears to have mezzanine.core in INSTALLED_APPS.

--
Stephen McDonald
http://jupo.org

[Doug Evenhouse]

Perhaps a big clue: when I attempt to run the Django shell I get this error:

Error: Could not import settings 'settings.development' (Is it on sys.path?): No module named development

[Stephen McDonald]

Ring any bells to you? Sounds like something you've configured previously, intentionally or otherwise.

[Doug Evenhouse]

I'm digging. On another project, in a separate virtualenv, I've got a settings module that partitions settings based on environment (development, staging, production) - this module seems to be leaking into my Mezzanine virtual environment somehow. I'll track this down. Looks like an environment issue on my end. Thanks for the help.

[Doug Evenhouse]

For what it's worth: I removed an old version of homebrew on my Mac, reinstalled an up-to-date version of homebrew and installed all new and updated python, virtualenv, etc and now the "quick start" instructions worked without a hitch. Looking forward to using Mezzanine.

-Doug