i use next approch for any number of envs:
- modifed CB/priv/rebar/boss_rebar.erl
- run ./rebar boss c=compile
- add {use_config, CONFIG_FILE}, in your PROJECT/boss.config to use another
env., example: {use_config, "boss.test.config"}, {use_config, "boss.test"},
{use_config, "boss.test-5.config"}, {use_config, "boss.test-5"},used in prod and env modes only in test modes the same approach remains %%% When running tests, you may want to create a separate configuration file %%% "boss.test.config" which, if present, will be read instead of boss.config. On Friday, May 30, 2014 3:09:14 PM UTC+4, David Welton wrote: > > I asked this on the Erlang list: > > http://erlang.org/pipermail/erlang-questions/2014-May/079310.html > > The ideal thing would really be to have a common config file, with > perhaps some kind of if/else for small differences. Or auxiliary > files for dev and production that contain additional configuration for > those. > > Thoughts? > -- > David N. Welton > > http://www.welton.it/davidw/ > > http://www.dedasys.com/ > -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/c2c90835-c665-48ca-9d4e-79c35d252261%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
boss_rebar.erl
Description: Binary data
