Home › Tutorials › Chrome, Server & Billing
Chrome, Server & Billing

The Upstream Server

#109 0:15 Part of the Rysh video series

rysh-server: the hub that routes shares between machines.

The Upstream Server — 0:15 walkthrough

What you'll see

  1. rysh-server is the optional collaboration hub local sessions connect to for sharing panes, groups, and tabs.
  2. Stack: Go/Gin API, PostgreSQL persistence, embedded NATS for real-time messaging, nginx in front.
  3. It handles JWT/Firebase auth and owns workspaces, members, API keys, and share routing/access control.
  4. Deploys as a Docker Compose stack: make dev-up for development, make prod-up for production.

Commands shown

echo 'rysh-server: collaboration hub -- routes shares across machines'
echo 'Stack: Go/Gin + PostgreSQL + embedded NATS + nginx'
echo 'Auth (JWT/Firebase) | workspaces | members | API keys | share routing'
echo 'Docker Compose: make dev-up (dev) / make prod-up (prod)'

Keys used

Enter

Transcript

0:00rysh-server: the hub that routes shares between machines.

0:05rysh-server is the optional upstream hub. Local sessions connect to it to share panes, groups, and tabs with collaborators on other machines.

0:15Under the hood it is Go and Gin for the API, PostgreSQL for persistence, an embedded NATS server for real-time messaging, and nginx out front.

0:26The server handles authentication with JWT or Firebase, and it owns workspaces, members, API keys, and the routing and access control for every share.

0:37It ships as a Docker Compose stack -- make dev-up for development, make prod-up for production -- so you can stand up your own hub in minutes.

Key takeaway
rysh-server is a Go/Gin + PostgreSQL + embedded NATS + nginx hub for auth, workspaces, and share routing, deployed via Docker Compose.