Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure vm.args via conform #19

Open
MSch opened this issue Feb 6, 2015 · 1 comment
Open

Configure vm.args via conform #19

MSch opened this issue Feb 6, 2015 · 1 comment

Comments

@MSch
Copy link

MSch commented Feb 6, 2015

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.

@bitwalker
Copy link
Owner

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 = test@127.0.0.1 which produces -name test@127.0.0.1.

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.).

Thoughts are welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants