Settings editable by admins #13
Labels
enhancement
New feature or request
Comments
|
yes please - on a per user basis, then if we have a collaboration partner we could add addition quota by agreement |
lkeegan
added a commit
that referenced
this issue
Oct 21, 2024
- add `Settings` model to database
- have a single instance of this in the database
- on startup create with default values if not already present in database
- add endpoints
- get `/settings` returns the settings
- used by frontend
- post `/admin/settings` overwrites the settings with the supplied values
- used by admin frontend
- allow admins to modify the settings in the frontend admin interface
- lists are represented as semi-colon delimited strings
- resolves #13
- also add `global_quota` to Settings, resolves #22
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Website settings such as default quota, delay between jobs etc should be stored in the database and modifiable in the admin interface
The text was updated successfully, but these errors were encountered: