lobehub/lobehub-gateway

최근 기록된 소스 활동: 2026년 7월 24일 02:32

SkillsMP 카탈로그 업데이트: 2026년 10월 29일 18:30

수집된 skills: 1

GitHub 스타: 27
GitHub 포크: 23

AI 어시스턴트로 설치

이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/lobehub/lobehub-gateway.

저장소 README

README 원본 파일: README.md

README 원본 보기

README 전체 펼치기

# LobeHub Gateway Go [简体中文](./README.zh-CN.md) `lobehub-gateway-go` is a Go reimplementation of the LobeHub gateway services. It is intended for self-hosted deployments that need a simple, single-instance gateway without Cloudflare platform bindings or external infrastructure dependencies. The original gateway implementations remain the protocol reference. This repository focuses on keeping the public HTTP and WebSocket behavior compatible while making the runtime easier to run as a normal Go service. ## Goals - Go implementation of LobeHub gateway protocols. - Single-instance design for straightforward self-hosting. - No Cloudflare Workers or Durable Objects dependency. - No Redis, PostgreSQL, NATS, or other external runtime services. - Keep protocol behavior compatible with the reference implementations where practical. ## Alignment Target The protocol baseline for this repository is the pair of standalone reference implementations: - `device-gateway` at `b0bbeab8fef29f7607f432f0cfa481409410dca8` - `agent-gateway` at `2986083b5c2e570ed3df0242c97532e556b62a70` For implemented gateway services, the target is compatibility with the public HTTP routes, WebSocket messages, request and response shapes, authentication behavior, routing semantics, and timeout behavior exposed by those reference implementations. This target intentionally keeps the Go runtime self-hosted and single-instance oriented. Device health sampling (`device_metrics`) and history queries (`POST /api/device/metrics`) are supported with up to 48 hours of bounded in-memory history. Restarting the gateway loses this history. The alignment target does not include the following capabilities: - Admin APIs and admin reporting. - Gateway management metrics. - Durable Object storage and WebSocket hibernation. - Multi-instance coordination. - Geo reporting. - Shared devices in LobeHub Workspace (team workspaces), workspace device pools, and workspace JWT routing. Only personal devices routed by `userId` are supported. - Experimental Labs features marked as alpha by upstream. ## Projects | Project | Status | Description | | --- | --- | --- | | [`device-gateway-go`](./device-gateway-go/README.md) | Implemented | Device gateway for routing LobeHub device connections, status queries, tool calls, system information, and agent-run requests. | | [`agent-gateway-go`](./agent-gateway-go/README.md) | Implemented | Agent gateway for relaying browser WebSocket sessions and server-pushed agent events. | ## Unified Binary The root module (`go.mod`) provides a unified entry point that starts both gateway services in a single process: ```text lobehub-gateway-go/ go.mod # umbrella module with replace directives cmd/gateway/main.go # unified entry: runs agent + device simultaneously agent-gateway-go/ gateway.go # facade re-exporting internal/gateway symbols go.mod # standalone module (unchanged) internal/gateway/ device-gateway-go/ gateway.go # facade re-exporting internal/gateway symbols go.mod # standalone module (unchanged) internal/gateway/ ``` Each sub-project remains an independent Go module and can be built/tested on its own. The root module uses `replace` directives to import the sub-modules via facade files (`gateway.go`) that re-export the internal package symbols. ### Build & Run ```bash # Build the unified binary go build -o gateway ./cmd/gateway # Run both services SERVICE_TOKEN=your-token ./gateway # Defaults: agent on :8787, device on :8788 # Override ports via env vars AGENT_PORT=9000 DEVICE_PORT=9001 SERVICE_TOKEN=your-token ./gateway ``` ### Environment Variables | Variable | Default | Shared | Description | | --- | --- | --- | --- | | `SERVICE_TOKEN` | — | Yes | Service auth token (required) | | `JWKS_PUBLIC_KEY` | — | Yes | JWKS public key for JWT verification | | `LOBE_API_BASE_URL` | `https://app.lobehub.com` | Agent only | LobeHub API base URL | | `AGENT_PORT` | `8787` | Agent only | Agent gateway listen port | | `DEVICE_PORT` | `8788` | Device only | Device gateway listen port | | `READ_TIMEOUT` | `30s` | Yes | HTTP read timeout | | `WRITE_TIMEOUT` | `1m` | Yes | HTTP write timeout | | `SHUTDOWN_TIMEOUT` | `10s` | Yes | Graceful shutdown timeout | The unified binary does not read `PORT`; each service's port is controlled only by `AGENT_PORT` / `DEVICE_PORT`. The standalone binaries keep using `PORT` (default 8787) as before. ### Release Artifacts Linux releases provide the unified binary and both standalone binaries for amd64 and arm64: ```text gateway-linux-amd64 agent-gateway-go-linux-amd64 device-gateway-go-linux-amd64 ``` Replace `amd64` with `arm64` for ARM systems. Standalone release asset names include the `-go` component. ### Docker Build and run the unified image locally: ```bash docker build -f docker/Dockerfile -t lobehub-gateway-go . docker run --rm \ -p 8787:8787 \ -p 8788:8788 \ -e SERVICE_TOKEN=your-token \ lobehub-gateway-go ``` Or start the provided Compose service: ```bash SERVICE_TOKEN=your-token docker compose -f docker/docker-compose.yml up -d --build ``` The Compose file uses the unified binary's default listener ports and forwards `SERVICE_TOKEN`, `JWKS_PUBLIC_KEY`, and `LOBE_API_BASE_URL`. To use custom listener ports or timeout values, add the corresponding variables from the table above to the Compose service's `environment` section and update its `ports` mappings when changing `AGENT_PORT` or `DEVICE_PORT`. The CD workflow publishes a multi-architecture image for linux/amd64 and linux/arm64. By default it is published as `ghcr.io/lobehub/lobehub-gateway:<version>`; repository maintainers can override the destination with the `DOCKER_IMAGE` Actions secret. Stable releases selected as the default version also publish the `latest` tag. ## Architecture This repository is organized as a collection of gateway services. Each gateway lives in its own directory so more gateway implementations can be added without coupling them to the existing services. The root module provides a unified binary that runs all gateways together. The current implementation style is intentionally minimal: state is held in memory, services run as ordinary HTTP/WebSocket servers, and deployment can be handled by systemd, Docker, Kubernetes, or any other process manager. ## Relationship To LobeHub Gateway Compared with the original LobeHub gateway projects, this repository has several deliberate differences: | Area | Original gateway | This repository | | --- | --- | --- | | Language | TypeScript | Go | | Runtime | Cloudflare Workers | Standard Go process | | Coordination | Durable Objects | In-memory single instance | | Platform binding | Cloudflare-specific | Platform-neutral | | Runtime dependencies | Cloudflare services | No external services required | Because this repository targets a single gateway instance, it does not provide distributed session coordination by default. If you need horizontal scaling, run one active gateway instance per routing domain or add a shared coordination layer explicitly. ## Development ### Unified binary ```bash # Build go build -o gateway ./cmd/gateway # Test root module (unified binary) go test ./... ``` ### Individual gateways Each gateway remains a standalone module and can be built/tested independently: ```bash cd agent-gateway-go && go test ./... cd device-gateway-go && go test ./... ``` See each gateway README for service-specific configuration, API routes, and local run instructions.

저장소 README를 불러오는 중…

이 저장소의 skills

소프트웨어 개발자

직업 카테고리 1개 · 100% 분류됨

skill

직업 분류

설명

업데이트

sync-upstream-gateway

소프트웨어 개발자

将本仓库的 Go gateway 实现与上游 LobeHub 参考实现（device-gateway / agent-gateway）以及应用侧客户端协议进行对齐。当需要同步上游协议、追平最新实现、或对齐到指定 LobeHub tag/commit 时调用。

원문 언어: 중국어

2026-07-24

수집된 skill 1개 중 1개를 표시합니다.