Refactor #100
Store Foreman Settings in the database and allow configure it using the WebUI/API
Description
Provide a mechanism to allow a user to have specific settings associated with them. This will supersede the current SETTINGS hash and allow overriding on a per user, per-model basis.
The idea is that there is a per_page setting at the system level, a per_page setting at the model level for each user and this should also allow for saving things like the user's search history and preferences.
Related issues
Associated revisions
fixes #100 - Setting is now a ActiveRecord object
This allows users to manage foreman settings via the UI.
the UI is a bit ugly, but works :)
splitted setting default data from the migration
this allows to add new data and modify its defaults
improved settings UI a bit more
refs #100
History
#1
Updated by Ohad Levy over 11 years ago
Updated by in the meanwhile, I've replaced $settings (global var) with a constant SETTINGS
#2
Updated by Ohad Levy almost 11 years ago
- Assignee changed from Martin Englund to Paul Kelly
As I know you already started some work on it, I'm reassigning it to you :)
#3
Updated by Paul Kelly over 10 years ago
Updated by - Subject changed from Turn $settings into a Ruby object to Provide a persistent user-specific settings object
#4
Updated by Ohad Levy about 10 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset 76607ed5fc692646c4b31791eea9c71a903e8f17.
#5
Updated by Ohad Levy about 10 years ago
- Subject changed from Provide a persistent user-specific settings object to Store Foreman Settings in the database and allow configure it using the WebUI/API
- Assignee changed from Paul Kelly to Ohad Levy
- Target version set to 0.4
switches global setting var to be a constant var - refs #100