no documentation for solid start --config-path or --config-file

Empieza ejecutando solid start --help y solid init, y luego sigue los puntos de entrada --config-path, --config-file y configFile para establecer su comportamiento. Actualiza la ayuda o la documentación de CLI pertinente para que la relación entre el directorio de configuración, el archivo de configuración y el ./config.json generado sea explícita, y verifica el comportamiento documentado con ambos comandos.

The output of solid start --help doesn't show any help description for the following items:

--config-path [value]
--config-file [value]

What's more, the output of solid init doesn't make this very clear either:

? Path to the config directory (for example: /etc/solid-server) ./myconf
? Path to the config file (for example: ./config.json) foo.json

When I see these items, I ask the following questions:

1. should the config file be stored in the config directory, or are these different things? I expected that the config file would be written as [config_dir]/[config_file], but it isn't. Is the config directory something for startup, or runtime configuration?
2. if I specify foo.json as a config file, why does solid init still write it to ./config.json?
3. I can specify a config file on the command line with solid start --config-file. If it reads this config file, what is the behaviour of the configFile option in this json file? Is it used at all (to reload a secondary config file?) or is it ignored?