Settings creation

[ErisDS]

From #567

When a specific setting is requested via GET, if it isn't found, we check to make sure it isn't specified in the default settings JSON, if it is, we return the default value and load that into the DB

When trying to create settings via PUT/POST, if a setting is not yet in the DB, we should again check if it is specified in the default settings JSON. If it is we should create it, but with the supplied value, if it isn't we probably should not create it for now.

We can add advanced permissions later for creating new settings? Although it really shouldn't be necessary as apps will have their own place to create settings.

[jgillich]

Assign to me please. :)

Any news about advanced permissions, are they required? Or how is it done for the apps?

[ErisDS]

Sorry @jgillich, @sebgie asked for this this one from me earlier, but I was on my way out the door and didn't get a chance to assign it.

[jgillich]

No problem. This is probably related to #1547 so I'm looking forward to getting it fixed. :)

[ErisDS]

Closing this in favour of the more comprehensive: #2061