You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: