It doesn’t look like they are still right as the config file is now renamed I think and also in its seperate folder?
Ive tried both renaming the file to the original configuration.json and also changing the file name to orthanc in the cmd line but in both cases I get errors related to the file or path?
Any easy suggestions on something I could try?
It doesn't look like they are still right as the config file is now
renamed I think and also in its seperate folder?
You can specify the configuration file name on the command-line or even
an entire directory (in which all JSON files will be loaded as Orthanc
configuration). In that way, the configuration file name didn't
actually change, and in fact it doesn't really matter (only that it
composed of one or more JSON files).
Ive tried both renaming the file to the original configuration.json
and also changing the file name to orthanc in the cmd line but in
both cases I get errors related to the file or path?
Can you specify which errors? Do check the path indeed, especially if
you're using a relative path (in which case check the working directory
of the process).
Any easy suggestions on something I could try?
Your question (subject) pertains to verbose logs, which are actually
unrelated to configuration (it's a command-line option switch). These
logs are written to standard output streams, which you're free to
redirect to files.