automaton-core.configuration

Liking cljdoc? Tell your friends :D

All platforms.

conf-state
read-param
start-conf
stop-conf

Configuration parameters, stored in configuration file. This namespace is the entry point to call conf

Design decision:

Configuration used to be based on outpace, it was too complicated for a small benefit,
The config.edn file was first unique, it needs to be updatable by environment to allow different value between production and repl, test and dev, but also monorepo vs app
The different version of parameter config.edn was first based on classpath (differentitated with aliases). It is ok for one app, but it renders the monrepo build complicated as it was naturally gathering all classpath, so all config.edn versions. The solution was to be based on environment parameter. So each alias can tell which version it uses, especially monorepo could be different.

Configuration parameters, stored in configuration file.
 This namespace is the entry point to call conf

Design decision:
* Configuration used to be based on outpace, it was too complicated for a small benefit,
* The `config.edn` file was first unique, it needs to be updatable by environment to allow different
value between production and repl, test and dev, but also monorepo vs app
* The different version of parameter `config.edn` was first based on classpath (differentitated
with aliases). It is ok for one app, but it renders the monrepo build complicated as it was naturally
gathering all classpath, so all `config.edn` versions. The solution was to be based on environment
parameter. So each alias can tell which version it uses, especially monorepo could be different.

raw docstring