[RFC] aurweb configuration
We'd like to sort out how we construct and use our $AUR_CONFIG options. Currently, we have a config.dev
and a config.defaults
. The config.dev
is used to override some of config.defaults
, but, this feels a bit hacky.
We should probably centralize all of our configurations in config.template
or something like that which just has comments about changing the fields that should be changed in production.
This issue is meant to iron out a concrete specification for the future of aurweb configs.
We'll start here by just farming some comments in regards to this and the description will be updated as those comments are discussed.
So, to start off: What kind of configuration(s) filesystem formats do you think would make the most sense for this project, and why?