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
Hi

Hi 🙂 I have opened the following issue on github None , but I think posting here would have been more appropriate so I will duplicate my issue here :

We were wondering if it is possible to set the default fileserver location on the side of the tracking server.
We have found this ticket #153 which explains how to do this client-side, but that would force all users and all Agents interacting with the Datasets to have credentials for the NAS. We would prefer to have the default fileserver location of the tracking server to be the NAS (for example mounted locally to the server). That may, we are assuming that the tracking server would the one handling the NAS communication and only it needs credentials.
Is this possible ?

Thanks in advance !

  
  
Posted one year ago
Votes Newest

Answers 4


I tried mounting azure storage account on that path and it worked: all files end up in the cloud storage

  
  
Posted one year ago

Worked like a charm 👌

  
  
Posted one year ago

if you are using a self hosted clearml server spin up with docker-compose, then you can just mount your NAS to /opt/clearml/fileserver on the host machine, prior to starting clearml server with docker-compose up

  
  
Posted one year ago

Sounds great, I'll try that 🙂

  
  
Posted one year ago
841 Views
4 Answers
one year ago
one year ago
Tags
Similar posts