-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
Currently, the frontend and backend are hosted together in the same project. To optimize bandwidth usage, consider separating the frontend and hosting it independently. This separation can also enhance scalability, improve deployment workflows, and potentially reduce server load on the backend.
Benefits of this approach:
- Saves bandwidth by reducing backend server load for static assets.
- Improves scalability by allowing independent updates for frontend and backend.
- Enables the use of optimized CDN services for serving frontend assets.
- Proposed Solution:
Deploy the frontend to a dedicated hosting service like GitHub Pages, Netlify, or Vercel.
Update the API endpoints in the frontend to point to the backend's hosted URL.
Ensure CORS is properly configured on the backend to allow requests from the new frontend domain.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels