Skip to content

Rename project from llm-proxy to proxy - #17

Open
joseconstela wants to merge 1 commit into
mainfrom
claude/rename-project-proxy-7vxhpv
Open

joseconstela wants to merge 1 commit into
mainfrom
claude/rename-project-proxy-7vxhpv

Conversation

@joseconstela

Copy link
Copy Markdown
Contributor

Summary

The repository moved to lab34-es/proxy, so this brings every reference in line with the new name — docs, Docker files, Go module, config defaults, and UI strings (31 files).

  • Go module: github.com/lab34/llm-proxy → github.com/lab34-es/proxy (now matching the actual repository host path), with all internal imports updated
  • Docker: binary, install path, and ENTRYPOINT renamed to proxy; default DSN is now /data/proxy.db
  • docker-compose: service and volume renamed; the image now points at ghcr.io/lab34-es/proxy:latest — fixing a pre-existing bug, since the publish workflow pushes to ghcr.io/${{ github.repository }} and the old ghcr.io/lab34/llm-proxy reference was never published
  • Docs & UI: README title, build commands and project tree; OpenAPI title and Swagger page title now read lab34/proxy, matching the console branding; dashboard footer reads "lab34 — proxy"; startup log prints proxy listening on :8080
  • .gitignore: entries renamed and root-anchored (/proxy, /proxy.db, …) — an unanchored proxy entry would have silently ignored new files under the internal/proxy/ package
  • coverage.out: regenerated by running the suite under the new module path

Deliberately unchanged

  • The llmp- API key prefix: it is a wire format, and renaming it would invalidate every already-issued key
  • Descriptive prose like "An OpenAI-compatible LLM proxy that routes…" — it describes what the software does, not its name
  • CI workflows — they already use ${{ github.repository }}

Test plan

  • Full Go test suite passes under the new module path (go test ./internal/...), coverage 83.8% — above the 80% CI gate
  • go vet clean; release binary builds (go build -trimpath -ldflags="-s -w" -o proxy .)
  • Frontend production build succeeds (npm ci && npm run build)
  • git check-ignore verified: root proxy binary ignored, internal/proxy/ package not ignored
  • Repo-wide sweep confirms no remaining name references (only descriptive "LLM proxy" prose and the intentional llmp- prefix remain)

🤖 Generated with Claude Code

https://claude.ai/code/session_01JbqwewzBjK9n16PKNFSrpC


Generated by Claude Code

The repository moved to lab34-es/proxy, so bring every reference in
line with the new name:

- Go module path becomes github.com/lab34-es/proxy (now matching the
  actual repository host path), with all internal imports updated
- Binary, default SQLite DSN, and Docker ENTRYPOINT renamed to proxy
- docker-compose service/volume renamed; the image now points at
  ghcr.io/lab34-es/proxy, which is where the publish workflow
  (ghcr.io/${{ github.repository }}) actually pushes
- README, OpenAPI title, Swagger page title, dashboard footer, and
  frontend README follow the lab34/proxy branding
- .gitignore entries renamed and root-anchored so the ignored proxy
  binary cannot shadow the internal/proxy package
- coverage.out regenerated under the new module path (full test suite
  passes at 83.8%)

The llmp- API key prefix is intentionally unchanged: it is a wire
format and renaming it would invalidate already-issued keys.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JbqwewzBjK9n16PKNFSrpC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants