#4306 (The inconvenience of changing a plugin config and/or site config on a production server.)

by Sharif Mehedi · in Developers · assigned to Sharif Mehedi

Summary

An example: When I put users.allow_online_registration to `True`, I immediately need to do a `pm prep` to make the database migrations for a few extra fields in the User model.

If we have many such plugin config and/or site config, then it might become irritating for a site operator when they need to tweak their site manipulating the configs that have dependent database fields.

Children

Comments

2 years, 7 months ago by Luc Saffre about #4306 (The inconvenience of changing a plugin config and/or site config on a production server.) : There are other things we can do to help site maintainers. For example a command to check whether a migration is needed. And then field descriptors (name, type, help_text) for the plugin settings.
2 years, 7 months ago by Luc Saffre about #4306 (The inconvenience of changing a plugin config and/or site config on a production server.) : Oops, I read this only now! Making database fields is not the only thing to depend on some plugin option. You can disable whole plugins in the settings.py file.
5 years, 1 month ago by Sharif Mehedi about #4306 (The inconvenience of changing a plugin config and/or site config on a production server.) : Maybe we should not make database fields dependent on a configuration option and have the fields already available on the database and only tweak the program features on such config change.