How to Get Vyne deployed
We publish a default docker-compose config at https://start.vyne.co.
This is a reasonable start for deploying a single-node Vyne environment, with a seperate schema server.
For now, Vyne requires Eureka for service discovery.
We're working on deploying Vyne natively on Kubernetes, without additional service discovery, which will be released in 0.21.
If you're interested in working with us as an early tester, please reach out on slack, as we'd love to work with you.
Vyne is packaged as a collection of container images, which need to be able to communicate between each other.
The following table outlines the components and, the default network addresses and ports that are expected to be exposed.
|Component & Image||Purpose||Optional component||Network address||Port(s)|
|Vyne||UI tooling and Query execution||Mandatory||http://vyne||80|
|Schema server||Central co-ordination of multiple schemas||Mandatory||http://schema-server||80 (http) |
|Analytics server||Stores query history and lineage||Optional||http://vyne-analytics-server||80|
When running with work-sharing enabled, Vyne also requires ports exposed to enable multicasting. See Clustered Deployment for more information
Vyne can be configured to work with Netflix / Spring Boot Eureka for client side service discovery.
Eureka support is disabled by default, and can be enabled by setting the
eureka.client.enabled=true flag on startup.