Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
We Are Hosting Our Own Clearml Server, And I Would Like Everybody In Our Team To Configure Their Clearml With

We are hosting our own ClearML server, and I would like everybody in our team to configure their ClearML with sdk.development.detect_with_pip_freeze=true

What is the easiest way to enforce this globally? Is it possible for me to modify the config snippet that is generated with app credentials?

Furthermore, the ClearML web server is re-configured to using port 80 (and not the default, 8080). When I do a clearml-init based on the generated config snippet, I am met with: Host port not detected, do you wish to use the default 8080 port n/[y]?

Is there a way for me to modify the config snippet to explicitly state port 80, so I don’t get this prompt?

  
  
Posted one year ago
Votes Newest

Answers 4


Regarding the config snippet - do you manually change it to port 80? I'm not sure how to configure this, maybe

might have some more insight.

I'm not sure this is possible in the open source version, but I'll try to find out 🙂

  
  
Posted one year ago

@<1523701279472226304:profile|SoreHorse95> , basically clearml-init tries to guess the port (which is usually 8080) - you should be able to just provide the new URL with the correct port instead

  
  
Posted one year ago

Hi SoreHorse95 , about enforcing a setting globally I think this option only exists in the Scale/Enterprise versions.

Regarding the config snippet - do you manually change it to port 80? I'm not sure how to configure this, maybe SuccessfulKoala55 might have some more insight.

  
  
Posted one year ago

CostlyOstrich36 Yes, I manually updated the port mapping in the docker-compose yaml. An alternative way would be to keep the 8080 port in the config, but then on the server forward all requests from 8080 to 80.

  
  
Posted one year ago
573 Views
4 Answers
one year ago
one year ago
Tags