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
Profile picture
FunnySeagull28
Moderator
5 Questions, 13 Answers
  Active since 10 January 2023
  Last activity one year ago

Reputation

0

Badges 1

13 × Eureka!
0 Votes
2 Answers
1K Views
0 Votes 2 Answers 1K Views
Is there a way to get a docker-compose.yml that would also work with a reverse proxy, such as traefik/nginx-proxy etc? Because otherwise I am not sure how I ...
4 years ago
0 Votes
0 Answers
906 Views
0 Votes 0 Answers 906 Views
It also seems a mess on the kubetnets helm install
4 years ago
0 Votes
0 Answers
876 Views
0 Votes 0 Answers 876 Views
Hey all, I followed the tutorial https://allegro.ai/docs/deploying_trains/trains_server_linux_mac/ . and also made sure I didn't miss anything with the https...
4 years ago
0 Votes
1 Answers
871 Views
0 Votes 1 Answers 871 Views
Ok, the more I dig in to this, the more I understand that unless this sits on a local network, its really not easy to get it to run securely
4 years ago
0 Votes
30 Answers
1K Views
0 Votes 30 Answers 1K Views
the path /opt/trains/data/elastic_7/nodes exists I can also see in the logs: trains_agent: ERROR: Failed getting token (error 401 from http://apiserver:8008 ...
4 years ago
0 Is There A Way To Get A Docker-Compose.Yml That Would Also Work With A Reverse Proxy, Such As Traefik/Nginx-Proxy Etc? Because Otherwise I Am Not Sure How I Can Host This

On the kubernets side I have ingress and ingressroute set up on EKS. With Traefik.
The services indeed uses ELB.'

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Ok, running now from:
https://trains.shapedo.com/dashboard

When the DNS populates it will also have letsencrypt sign it. so I have https and a password protected login

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Needs quotes:
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.apiserver.environment.TRAINS__APISERVER__ELASTIC__UPGRADE_MONITORING__V16_MIGRATION_VERIFICATION contains false, which is an invalid type, it should be a string, number, or a null

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Happend again after restarting the container.

Where does one add apiserver.elastic.upgrade_monitoring.v16_migration_verification flag set to false?

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Question, I see at the end of the docker-compose file:
networks:
backend:
driver: bridge
I want to change it to:

networks:
default:
external:
name: nginx-proxy

Will that break it?

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Ok - how do I set the API server to a on the web-UI to a different path? Because the api-server needs to be also https, you can't mix calls

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

Yes looks great, thanks!
First thing though is I am going put it behind an nginx-proxy because there seems to be no ACL

4 years ago
0 The Path /Opt/Trains/Data/Elastic_7/Nodes Exists I Can Also See In The Logs: Trains_Agent: Error: Failed Getting Token (Error 401 From

ah no, same issue with IPS:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://108.128.174.211:8008/v2.9/auth.fixed_users_mode .

4 years ago