Actions
Refactor #100
closed
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.
Updated by Ohad Levy over 15 years ago
in the meanwhile, I've replaced $settings (global var) with a constant SETTINGS
Updated by Ohad Levy over 14 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 :)
Updated by Paul Kelly about 14 years ago
- Subject changed from Turn $settings into a Ruby object to Provide a persistent user-specific settings object
Updated by Ohad Levy about 14 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset 76607ed5fc692646c4b31791eea9c71a903e8f17.
Updated by Ohad Levy about 14 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
Actions