You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/basho/cuttlefish supports generating the vm.args from the app.conf, is something similar planned for conform? Just being able to set the node name and cookie would already solve all my problems.
The text was updated successfully, but these errors were encountered:
I would like to support this yes. I'd like some thoughts on the best approach to implementing this though, since we want a single source config file, but produce two output files. How do we indicate which mappings go to which file? It could be a mapping property which defines the output file, or perhaps we should have a special prefix key for vm.args mappings, such as erlang.vm.name = [email protected] which produces -name [email protected].
I'm not sure on what the best approach will be in order to keep things flexible in the future. I want to keep conform abstracted at the level of .conf. -> conversion/translation plugin (i.e. converts the parsed conf to Erlang config terms) -> output format generator (i.e. write datastructure as Erlang terms, or perhaps Elixir terms, or as a new conf format like vm.args, etc.).
https://github.com/basho/cuttlefish supports generating the
vm.args
from theapp.conf
, is something similar planned for conform? Just being able to set the node name and cookie would already solve all my problems.The text was updated successfully, but these errors were encountered: