zorven
EN
TürkçeEnglish日本語中文
Sign in Start free
Release 0.3.4 - 0.3.5

Zorven 0.3.4: gRPC through tunnels, new Windows installer and multi-node groundwork

Your client updates automatically; run zorven update to update manually. The CLI and the desktop app ship with the same version number. The macOS desktop app stays at 0.3.2 in this release.

gRPC through tunnels

  • gRPC now works through the tunnel: unary, server-streaming, client-streaming and bidi streams; the grpc-status and grpc-message trailers reach the client. grpc-web already worked.
  • No setup needed: zorven http 50051 is enough. The agent forwards gRPC requests to your local service over HTTP/2 (h2 for https:// targets, h2c for http://). Pin it with --origin-protocol auto|http1|h2|h2c or --h2c if you prefer.
  • gRPC traffic counts towards the bandwidth quota and the request log. gRPC needs client 0.3.4; on an older client, gRPC requests get a descriptive UNAVAILABLE response and other traffic is unaffected.
  • Limit: request trailers are not carried.

New Windows installer

  • 0.3.5 fix: in the 0.3.4 installer the desktop app and the CLI collided on the same file name, so the desktop app would not open (a console window said "this is a command line tool"). The desktop app is now installed as ZorvenDesktop.exe. If you installed with the 0.3.4 Setup, just run the 0.3.5 Setup again; it repairs the installation.
  • Zorven Setup is now a real installer: with admin approval it installs to Program Files\Zorven, places the CLI (zorven.exe) next to it and adds the folder to the system PATH.
  • Start menu shortcut: Zorven shows up in taskbar search; optional desktop shortcut.
  • One mode: the installer no longer asks "service or command line". Zorven always runs as a background service; the desktop app shows and manages it. Signing in hands your credentials to the service.
  • "Add or remove programs" entry and clean removal (Zorven.exe --uninstall); your settings are kept.
  • Updates replace the desktop app and the CLI together. An older per-user installation is migrated on first install.
  • The installer is unsigned; on the SmartScreen prompt choose "More info > Run anyway".

Client

  • Node list and failover: the agent receives the list of nodes from the server, picks the closest one and switches to another if the connection drops. zorven status shows the connected node. If you pin the server with zorven config set server, the list is not used.

Infrastructure (hosted service)

  • Groundwork for multi-node (edge) infrastructure: verified mTLS between nodes, signed configuration publishing, inter-node WebSocket and raw TCP/UDP forwarding, edges that keep serving during a database outage, readiness and metrics endpoints. These come into play as regions are added; nothing visible changes in today's service.
  • Clients reconnecting during a database outage no longer stop permanently; they retry.
  • A renewed wildcard certificate takes effect without restarting the server.

← All updates