Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better document usage #40

Open
merwok opened this issue Jan 24, 2017 · 0 comments
Open

Better document usage #40

merwok opened this issue Jan 24, 2017 · 0 comments

Comments

@merwok
Copy link

merwok commented Jan 24, 2017

Hello! I have some bits of config that can change by environment but are not secrets, and need to be editable without code changes and deployment. On a previous project, we had a custom model (with a small number of fields for our config buts) linked to sites.Site that did the job well. I thought dbsettings could be an easier and more powerful way (thanks to the included types) to do this, but it seems like I’m misunderstanding something in the docs.

After defining a class (with two settings without default values) and running migrations, I don’t see anything in the edit view. Is it mandatory to reference the settings from another model? Or is there some code I’m missing to make my settings appear in the admin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant