mmc/lingma-proxy-compose
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Switch remote deploy to vendored source builds

Browse Source 
Move remote deployment to a vendored source bundle built on the target host via Docker so redeploys no longer require local cross-compilation or host Go installation.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
GitHub Actions
2026-05-08 12:19:18 +08:00
parent bb27566e38
commit c1a0fe2949
1320 changed files with 497125 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@@ -252,9 +252,17 @@ Use this when VS Code / the Lingma plugin is already running, when you want plug
### CLI
Run directly from source:
```bash
git clone https://github.com/Lutiancheng1/lingma-proxy.git
cd lingma-proxy
go run ./cmd/lingma-ipc-proxy --host 127.0.0.1 --port 8095 --session-mode auto
```
Build an explicit binary only when you want one:
```bash
go build -o ./dist/lingma-proxy ./cmd/lingma-ipc-proxy
./dist/lingma-proxy --host 127.0.0.1 --port 8095 --session-mode auto
```
@@ -266,6 +274,20 @@ Windows:
.\dist\lingma-proxy.exe --host 127.0.0.1 --port 8095 --session-mode auto
```
### Server Deployment Without CI
For Linux servers where you do not want to cross-compile locally, check in `vendor/` and let the target host build from source:
```bash
go mod vendor
REMOTE_HOST=150.158.105.6 \
REMOTE_USER=root \
REMOTE_PASSWORD='your-password' \
./scripts/deploy-remote.sh
```
The script uploads `cmd/`, `internal/`, `vendor/`, `go.mod`, and `go.sum`, prepares a Docker build context on the server, then rebuilds the runtime image there with a multi-stage Docker build. The remote host needs `docker`, `tar`, and `curl`; it does not need a host Go installation, but it does need network access to pull the base Docker images if they are not already cached.
## Client Configuration
### Claude Code