Skip to content

chore: remove hardcoded Vite proxy IP - #61

Merged
DeepZone merged 1 commit into
mainfrom
codex/remove-hardcoded-vite-proxy-ip
May 22, 2026
Merged

chore: remove hardcoded Vite proxy IP#61
DeepZone merged 1 commit into
mainfrom
codex/remove-hardcoded-vite-proxy-ip

Conversation

@DeepZone

Copy link
Copy Markdown
Owner

Motivation

  • The frontend Vite dev proxy contained a hardcoded private IP (http://192.168.58.167:8000) which breaks portability for self-hosters and must not be committed.
  • Make the proxy target configurable via environment variables so different deployments can use their own hostnames/IPs without code changes.

Description

  • Replaced the hardcoded proxy in frontend/vite.config.ts with an environment-driven value const apiProxyTarget = process.env.VITE_API_PROXY_TARGET || 'http://backend:8000' and set target: apiProxyTarget.
  • Added VITE_API_PROXY_TARGET=http://backend:8000 to .env.example to document the frontend Vite proxy default.
  • Updated README.md selfhosting/networking guidance with Docker Compose and local development defaults and an explicit note to avoid committing local/private IPs.
  • Searched the repository for private IP patterns (192.168.*, 10.*, 172.16-31.*) and removed the single tracked occurrence from the frontend config.

Testing

  • Built the frontend with cd frontend && npm run build, which completed successfully and produced the production build.
  • Ran backend tests with cd backend && pytest -q, and the test suite passed (102 passed).

Codex Task

@DeepZone
DeepZone merged commit 7d3704e into main May 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant