Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #3179] [CLOSED] Add Vite proxy configuration to forward requests to backend #4229

New Issue
Closed
opened 2026-02-22 18:35:24 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:35:24 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/3179
Author: @kittors
Created: 2/12/2025
Status: ❌ Closed

Base: master ← Head: feat/vite-proxy-setup

📝 Commits (1)

  • f41675b Add Vite proxy configuration to forward requests to backend

📊 Changes

2 files changed (+89 additions, -69 deletions)

View changed files

📝 frontend/vite.config.js (+80 -69)
➕ pnpm-lock.yaml (+9 -0)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

What is in this change?

  • Added Vite proxy configuration to forward requests to the backend at http://localhost:3001.
  • Configured Vite server to listen on port 3000 and forward requests matching the VITE_API_BASE environment variable to the back-end API.

Additional Information

  • This change is mainly for local development, enabling the Vite development server to act as a proxy to an existing backend server.
  • I think you can update the VITE_API_BASE in .env to "/api".

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/3179 **Author:** [@kittors](https://github.com/kittors) **Created:** 2/12/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `feat/vite-proxy-setup` --- ### 📝 Commits (1) - [`f41675b`](https://github.com/Mintplex-Labs/anything-llm/commit/f41675b7cb1bcb3871fe6024ccc2c1d5eaba680e) Add Vite proxy configuration to forward requests to backend ### 📊 Changes **2 files changed** (+89 additions, -69 deletions) <details> <summary>View changed files</summary> 📝 `frontend/vite.config.js` (+80 -69) ➕ `pnpm-lock.yaml` (+9 -0) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [x] ✨ feat - [ ] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> - Added Vite proxy configuration to forward requests to the backend at `http://localhost:3001`. - Configured Vite server to listen on port `3000` and forward requests matching the `VITE_API_BASE` environment variable to the back-end API. ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> - This change is mainly for local development, enabling the Vite development server to act as a proxy to an existing backend server. - I think you can update the VITE_API_BASE in .env to "/api". --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:35:24 -05:00
yindo closed this issue 2026-02-22 18:35:24 -05:00
yindo changed title from [PR #3179] Add Vite proxy configuration to forward requests to backend to [PR #3179] [CLOSED] Add Vite proxy configuration to forward requests to backend 2026-06-05 15:17:29 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#4229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?