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, I Have A Self-Hosted Instance Running Quite Well, Pretty Good Job. I'M Wondering If There Is Any Way To Have A Read-Only User? Is It Available In The

Hi, I have a self-hosted instance running quite well, pretty good job. I'm wondering if there is any way to have a read-only user? Is it available in the apiserver.conf where I defined my fixed_users ?

  
  
Posted 3 years ago
Votes Newest

Answers 6


AgitatedDove14 This is what I expected for the community version. It would really nice to have a read-only link. My use case is when I have a merge request for a model modification I need to provide several informations for our Quality Management System one is to show that the experiment is a success and the model has some improvement over the previous iteration. Obviously I don't want the reviewer to see all my failed experiments 😉 . So yes it should be really nice to have read-only share link for specific experiement.

  
  
Posted 3 years ago

Hi SteadyFox10
Short answer no 😞
Long answer, full permissions are available in the paid tier, along side a few more advanced features.
Fortunately in this specific use case, the community service allows you to share a single (or multiple) experiments with a read-only link. Would that work ?

  
  
Posted 3 years ago

My use case is when I have a merge request for a model modification I need to provide several informations for our Quality Management System one is to show that the experiment is a success and the model has some improvement over the previous iteration.

Sounds likes good approach 🙂

Obviously I don't want the reviewer to see all ...

Maybe move publish the experiment and move it to a dedicated folder ? Then even if they see all other experiments, they are under "development" project, so that when you send the link, they (QC) can compare the latest published experiment with the previous one ?
SteadyFox10 would that work ?

  
  
Posted 3 years ago

Yes this will work I think.

  
  
Posted 3 years ago

Hurray 🙂
BTW: the next version will have a project level "readme alike" markdown embedded in the UI, so hopefully you will be able to add all the graphs there :)

  
  
Posted 3 years ago

Oh can't wait to see this feature 👀

  
  
Posted 3 years ago
647 Views
6 Answers
3 years ago
one year ago
Tags