Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#16968 closed Bug (needsinfo)

Cannot use runserver without definig default database

Reported by: Yaşar Arabacı Owned by: nobody
Component: Core (Management commands) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no



In latest source, you cannot use runserver command without defining a default database settings because imports django.db. I thought this may be a design decision, but I am opening a ticket just in case it is not.

Change History (2)

comment:1 Changed 7 years ago by Simon Charette

Resolution: needsinfo
Status: newclosed

Hi yasar!

Is it possible that you provide more info concerning the issue because it actually works for me doing the following:

(trunk)simon@simon-laptop:~/Bureau$ startproject ticket_16968
(trunk)simon@simon-laptop:~/Bureau$ cd ticket_16968/
(trunk)simon@simon-laptop:~/Bureau/ticket_16968$ ./ validate
0 errors found
(trunk)simon@simon-laptop:~/Bureau/ticket_16968$ ./ runserver 
Validating models...

0 errors found
Django version 1.4 pre-alpha SVN-16921, using settings 'ticket_16968.settings'
Development server is running at
Quit the server with CONTROL-C.

Plus browsing to provides some useful information telling that you can actually run a django instance without interacting with a db:
If you plan to use a database, edit the DATABASES setting in ticket_16968/

comment:2 Changed 7 years ago by Yaşar Arabacı

I guess there was something in my installed apps that needed to use database in the time I was trying to runserver. Ticket can be closed.

Note: See TracTickets for help on using tickets.
Back to Top