Page MenuHomePhabricator

Allow config options to be bound to applications
Closed, WontfixPublic

Description

  • When a config option applies to a specific application, we can bind it to the application.
  • For installed applications, we could show a link ("This affects __Harbormaster__.").
  • For uninstalled applications, we could show a warning ("This affects Harbormaster, but the application is not currently installed.").

In the Config application you can see and change settings for applications that are not installed (for example Harbormaster and Releeph).

These should not be shown unless the application is installed.

Event Timeline

Mnkras raised the priority of this task from to Needs Triage.
Mnkras updated the task description. (Show Details)
Mnkras added a project: Applications.
Mnkras added a subscriber: Mnkras.

I don't see the value here in hiding, as admins are likely to want to explore and learn about other apps. We should show a notice though that this application is not installed.

That works as well, what about making them immutable unless they are installed?

epriestley renamed this task from Hide config settings for uninstalled applications to Allow config options to be bound to applications.Feb 17 2015, 4:32 PM
epriestley updated the task description. (Show Details)
eadler added a project: Restricted Project.Aug 5 2016, 5:23 PM
epriestley claimed this task.
epriestley added a subscriber: epriestley.

I think most of these are just moving into Application configuration over time, which tends to be a bit easier to use. I expect to just continue that trend in the future and this probably isn't worth building separately. I can't recall too much other confusion, and most of these are called <appname>.stuff anyway, which is fairly not-misleading.