service & bridge
The service group manages polyglot services and generates cross-language
service bridges — a protocol contract plus typed clients that let services
written in different languages talk to each other safely.
re-shell service --help| Subcommand | Purpose |
|---|---|
bridge | Generate cross-language service bridges (contract + typed clients) from the workspace v2 config. |
polyglot | Build and deploy polyglot full-stack applications. |
run (alias svc) | Manage development services. |
service bridge generate
Section titled “service bridge generate”Usage: re-shell service bridge generate [options]
Generate a service bridge: a protocol contract (.proto/OpenAPI/GraphQL SDL)plus a typed TS client and a documented Python scaffoldre-shell service bridge generateWhat it produces:
- A protocol contract — gRPC
.proto, OpenAPI, or GraphQL SDL. - A typed TypeScript client that is type-checked against your installed
tsc. - A documented Python client scaffold.
The generator reads your declarative re-shell.workspaces.yaml (v2) to know
which services exist and how they relate, so the bridge matches your real
topology. Async transports (Kafka/Redis Streams), circuit breakers, and
distributed tracing are scaffolded as types and stubs — see the
Roadmap for status.
Managing development services
Section titled “Managing development services”# Run / manage local development servicesre-shell service run --help
# Build and deploy a polyglot applicationre-shell service polyglot --helpSee also
Section titled “See also”- generate backend — scaffold the services a bridge connects.
- api — OpenAPI specs and clients.
- k8s / Helm / GitOps — deploy the services.