if there is no clearml.conf on the system, then the script with
Task.init("a", "b") will create project "a" and task "b" on demoapp server.
User can also do the following:
Task.set_credentials(...) Task.init("a", "b")and now it will go to provided api_host etc, still without clearml.conf file.
Now, I would like to raise an issue if api_host is the default one (the one when without clearml.conf file) and thus tracking is going to public demoapp server.
But actually, there can be few workarounds:
check if "~/clearml.conf" exists or not use
set_credentials to explicitly setup the server.
I was just wondering if we could have a flag though in
Task to prevent logging to demoapp...
it would raise an error if the env where execution happens is not configured to track things on our custom server to prevent logging to the public demo server ?
What do you mean by that? catching the default server instead of the configured one ?
I see TightElk12
You can always setup the OS environments : CLEARML_API_HOST CLEARML_WEB_HOST CLEARML_FILES_HOST with the correct configuration Or you can simply set CLEARML_NO_DEFAULT_SERVER=1 which will prevent any usage of the default demo serverwdyt?