Opened 19 years ago
Closed 19 years ago
#176 closed defect (invalid)
Database settings should not be kept in settings.main for ease of packaging.
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Tools | Version: | |
| Severity: | normal | Keywords: | django-admin database settings distribution |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I'm currently developing a project which I hope will be reusable. This obviously includes a certain amoutn fo setting thins up in settings.main. However, when it comes to packaging this project, I'm goign to have to keep remembering to remove my database setting from the file before uploading. Ditto if I want to keep my project in a public svn repository.
I propose moving the database settigns by default to settings/db.py which will be imported from within main.py
This file will be created by django-admin startproject but a new command should be added to just add the skeleton db.py file to projects that have been distributed without it.
Change History (2)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Hmm, now I've played with it a bit more, I get it. No need to change. Sorry for the bother.
Looking at it, it's a bit more complex than that, isn't it?
I suppose what I'm trying to do is remove things like INSTALLED_APPS from the main settings file.
Or maybe I'm just not getting how to distribute an application.