trinquet uses gRPC for its messaging protocol. The trinquet project includes a gRPC-based Go client and a command line utility, trinquetctl, for communicating with the trinquetd server.
For languages with no gRPC support, trinquet provides a JSON grpc-gateway. This gateway serves a RESTful proxy that translates HTTP/JSON requests into gRPC messages.
It exports metrics for Prometheus
Distributed tracing is available using OpenTracing. Supported tracers are:
You can download the binaries :
- Architecture i386 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture amd64 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture arm [ linux / freebsd / netbsd ]
- Architecture i386 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture amd64 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture arm [ linux / freebsd / netbsd ]
- Architecture i386 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture amd64 [ linux / darwin / freebsd / netbsd / openbsd / windows ]
- Architecture arm [ linux / freebsd / netbsd ]
Launch Zipkin with Docker, and open a browser on 9411:
$ docker run -d -p 9411:9411 openzipkin/zipkin
or Jaeger with Docker (open a browser on 16686):
$ docker run -d -p5775:5775/udp -p16686:16686 jaegertracing/all-in-one:latest
Use the trinquetd CLI to launch a server:
$ trinquetd run -config trinquet.toml -v 2 -logtostderr
Use the trinquetctl CLI to manage pelota informations.
Use the trinquetadm CLI to manage the server.
You could explore the API using Swagger UI :
http://localhost:9090/swagger-ui/
-
Initialize environment
$ make init
-
Build tool :
$ make build
-
Launch unit tests :
$ make test
See CONTRIBUTING.
See LICENSE for the complete license.
A changelog is available
Nicolas Lamirault nicolas.lamirault@gmail.com