Rename project from llm-proxy to proxy - #17
Open
joseconstela wants to merge 1 commit into
Open
joseconstela wants to merge 1 commit into
joseconstela wants to merge 1 commit into
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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).github.com/lab34/llm-proxy→github.com/lab34-es/proxy(now matching the actual repository host path), with all internal imports updatedENTRYPOINTrenamed toproxy; default DSN is now/data/proxy.dbghcr.io/lab34-es/proxy:latest— fixing a pre-existing bug, since the publish workflow pushes toghcr.io/${{ github.repository }}and the oldghcr.io/lab34/llm-proxyreference was never publishedlab34/proxy, matching the console branding; dashboard footer reads "lab34 — proxy"; startup log printsproxy listening on :8080.gitignore: entries renamed and root-anchored (/proxy,/proxy.db, …) — an unanchoredproxyentry would have silently ignored new files under theinternal/proxy/packagecoverage.out: regenerated by running the suite under the new module pathDeliberately unchanged
llmp-API key prefix: it is a wire format, and renaming it would invalidate every already-issued key${{ github.repository }}Test plan
go test ./internal/...), coverage 83.8% — above the 80% CI gatego vetclean; release binary builds (go build -trimpath -ldflags="-s -w" -o proxy .)npm ci && npm run build)git check-ignoreverified: rootproxybinary ignored,internal/proxy/package not ignoredllmp-prefix remain)🤖 Generated with Claude Code
https://claude.ai/code/session_01JbqwewzBjK9n16PKNFSrpC
Generated by Claude Code