Config should be persistent and updated via the HTTP api

[benoitc]

in relation to #10

I'm thinking to add a config file in the release that would contain the main settings and containers descriptions.

[nrdufour]

There is already a support for a configuration via application environment.
You can define storages in app.config. Look at https://github.com/refuge/coffer/blob/master/src/coffer_server.erl#L68.

Now perhaps this part could be refactored to have a full fledged config file like http port and other options.

[benoitc]

@nrdufour this is already the case, you can define the conf and such but this isn't really human friendly imo. Also it can't be easily update via HTTP.

I suggest either to use INI or toml [1] as config formatI.

Example of config:

[core]
...

[storage "foo"]
backend = coffer_storage_ets
...

Ip, ports could still be configred in the app.config file. Note that if we can easily update the app.confi using HTTP I'm fine for it. Thought?

[1] https://github.com/mojombo/toml

[nrdufour]

I like a lot toml one for sure.

It would be consistent to have just one config file for all.

[benoitc]

+1 for the consistency.

[benoitc]

We need to define which configuration will be persistent or not.

Items that I see persistent are:

• addresses on which coffer is listening (+ ssl config for them)
• storages configurations
• replication configurations (if we need them persistent)

In yesterday discussion we discussed the possibility to have a database storing these configs informations. Maybe it isn't needed for a start. We could use econfig to manage the config in a configuration file. Eventually econfig can be updated to support toml. To make things easier we can also make the config system pluggable with a default to the config file.

Thoughts?

[nrdufour]

I like the idea of starting simple with econfig.
The 3 items you mentioned are clearly the ones to go there.

So let's move on with econfig.