lmarini and I discussed the Pro's and Con's of doing this.

Advantages:

• Geodashboard could be updated by Medici users, without having to update code in app.config
• Extractors could add data to the config dynamically. Example: the Geoserver Layers extractor could be adding the layer ID to app.config.layers.
• In theory, Medici-Play could deliver the app.config through Scala, without the need for an Ajax call

Challenges:

• Right now, Geodashboard is dependent on Medici, but we wouldn't want Medici to be dependent on Geodashboard.
• I'm not sure if we would be able to extract, for example, the Parameters from the sensors.

We've talked about just uploading the app.config to Medici, and fetching it as a single file. At the moment, that would actually slow down loading of Geodashboard, because the app.config is concatenated into the app.js before the application is loaded. And if we did that now, we would have to wait on the Ajax call to get the config before we could proceed.

It just seems like there is potential here to make this more manageable directly through a Medici admin interface, but we'd have to identify each of these issues and iterate a bit.