Github user nickva commented on the issue:
https://github.com/apache/couchdb-chttpd/pull/144
Alright, good points, agree. If it's worth doing, it's worth doing right.
Here is what I came with as first thing:
* Don't add a new application, it would be silly.
* Stick it in config application. It seems like a configuration-y thing.
* 3 new functions. API looks like
- `config:features() -> [<<"feature1">>, <<"feature2">>, ...].`
- `config:feature_enable(<<"feature1">>).`
- `config:feature_disable(<<"feature2">>).`
* Applications enable features and disable them. Then `chttpd` reads list
of features from config and shows them in the welcome message.
* Behind the scenes it is really just writing to config "[features]"
section a bunch of booleans. With persistence set to `false`.
* Users can directly set "features" in the config file transparently.
The advantage is it doesn't reinvent the world. Takes advantage of config
server (so applications can monitor for changes and such if needed).
( Added same comment to https://issues.apache.org/jira/browse/COUCHDB-3180 )
@rnewson I'll give this a try and see what it looks like
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
