Menu
▾
▴
6020-Specifying configuration file
Specifying configuration file
As mentionned in the parameters description, you may force Mylene to use a configuration file in particular using for example the parameter --config-file=filename.ini
To accomodate portable installation and other complex setup, please note that regarding that filename it may:
- incorporate environment variables
- In the following example, the parameter is specifying to use a configuration file from a base location coming from an environment variable:
- --config-file="%PAL:DataDir%\settings\Filename with spaces.ini"
- In the following example, the parameter is specifying to use a configuration file from a base location coming from an environment variable:
- relative to current path
- The given configuration filename does not have to be in aboslute format. It could be relative. When it's relative, it relative to the current working directory when the Mylene is started. It is not relative to the executable itself! So if for example you're in your desktop folder, you launch Mylene from a "Program Files(x86)" folder and you specify a relative filename like "--config-file=VariousConfigStuff\Mylene\BasicConfig.ini", the "RelativePath" won't be search from the "Program Files(x86)" but from the desktop one.
- --config-file="VariousConfigStuff\Mylene\BasicConfig.ini"
- The given configuration filename does not have to be in aboslute format. It could be relative. When it's relative, it relative to the current working directory when the Mylene is started. It is not relative to the executable itself! So if for example you're in your desktop folder, you launch Mylene from a "Program Files(x86)" folder and you specify a relative filename like "--config-file=VariousConfigStuff\Mylene\BasicConfig.ini", the "RelativePath" won't be search from the "Program Files(x86)" but from the desktop one.
As you can see with the above example, if the configuration path or filename has spaces in it, you may enclose the value of it between quotes.
When you launch the application specifying the configuration filename, the complete path and filename does not have to exists actually. Regarding the path, if a few branches of directories need to be created, they will, as long as it is possible. Obviously, application won't invent inexisting drive, inexisting network server or won't write in folder where the current user has no rights to write in.
It's when Mylene is closed, that it will create the file if it was not present or will update the one there if it was.
You may determine for sure what is the actual configuration file Mylene is using by going in the "About..." page and look for the line "Config file" as shown in the image below:
