Configuration store

[Lovinity]

Transform sails.config.custom into a configuration store so that configuration can be modified from DJ Controls.

- [ ] Create a node-convict schema and replace sails.config.custom with the new schema. Probably best to delete the file all together and put the node-convict into a global variable for the application, initialized by bootstrap.js. REJECTED: Using our own implementation of easy-config-store instead, and maintaining sails.config.custom (but with easy-config, changes to properties will be saved to disk and re-loaded whenever the application loads).

- [ ] Modify all instances / uses of sails.config.custom to use the new convict store. Not necessary with easy-config-store

• [x] Implement endpoints in config/* for getting and updating configuration. Configuration updating should require director authentication. Configuration getting should require host authorization.

• [x] Run final tests of everything

After completion, DJ Controls should have some configuration windows built to utilize the new endpoints and allow directors to modify configuration.

[Lovinity]

So far, tests seem favorable. But not everything has been tested yet as not everything was implemented in DJ Controls.