Am 11.10.2016 um 18:01 schrieb Alessandro Bianciotto:
Hi everybody,
I'm using the vibe.core.args package to process custom-defined command-line arguments that I define in the default json configuration file "vibe.conf": things work just fine here, but I'm wondering whether there's a way to define a different name/path for this file (e.g. having it as foo/bar.conf, or whatever). Shall I edit the package's source code or is there a way to configure this?
Currently the path is fixed and the sources would have to be edited
manually. The problem is that the file is read before any application
code is run (vibe.core.core's shared static this is the first to
trigger the lazy config file load).
One possibility would be to define an environment variable that can be
set, another would be to add the possibility to add additional
configuration files in /etc/vibe.conf (or using a command line option).
Alternatively, an API function that loads an additional configuration
file could be added, but it would only work for options that are read
after the function was called, which excludes any of vibe.d's default
options.