github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

Proposal for RAG API Template with Frontend and Backend #706

New Issue
Closed
opened 2026-03-07 21:22:22 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-07 21:22:22 -06:00
Owner
Copy Link

Originally created by @Perpetue237 on GitHub (Jun 18, 2024).

Introduction:

I want to propose the addition of a template for building a Retrieval-Augmented Generation (RAG) API with a frontend and backend using Docker Compose. RAG is a powerful technique that combines retrieval-based methods with generation-based methods to improve the quality and relevance of generated responses, making it highly useful for applications like question-answering, chatbots, and more.

Proposal:

The proposed template will consist of a backend service for handling the RAG model, a frontend for interacting with the API, and an optional Nginx service for routing and load balancing. The template will use popular technologies such as Python (FastAPI) for the backend, React+Vite for the frontend, and Docker Compose to orchestrate the services and mount external volumes where the LLMs are stored.

Benefits:

  • Ease of Deployment: Simplifies the deployment of a RAG-based application with a predefined template.
  • Reusability: Provides a reusable template for developers to set up an RAG application quickly.
  • Scalability: Utilizes Docker Compose to efficiently manage and scale the services.

Example Structure:

rag-api-template/
├── backend/
│ ├── Dockerfile
│ ├── app/
│ │ ├── main.py
│ │ ├── models/
│ │ └── utils/
├── frontend/
│ ├── Dockerfile
│ ├── src/
│ │ ├── App.tsx
│ │ ├── components/
│ │ └── styles/
├── nginx/
│ ├── nginx.conf
├── docker-compose.yml
└── .env

I would love to hear feedback and suggestions from the maintainers and the community on this proposal.

Originally created by @Perpetue237 on GitHub (Jun 18, 2024). **Introduction:** I want to propose the addition of a template for building a Retrieval-Augmented Generation (RAG) API with a frontend and backend using Docker Compose. RAG is a powerful technique that combines retrieval-based methods with generation-based methods to improve the quality and relevance of generated responses, making it highly useful for applications like question-answering, chatbots, and more. **Proposal:** The proposed template will consist of a backend service for handling the RAG model, a frontend for interacting with the API, and an optional Nginx service for routing and load balancing. The template will use popular technologies such as Python (FastAPI) for the backend, React+Vite for the frontend, and Docker Compose to orchestrate the services and mount external volumes where the LLMs are stored. **Benefits:** - **Ease of Deployment**: Simplifies the deployment of a RAG-based application with a predefined template. - **Reusability**: Provides a reusable template for developers to set up an RAG application quickly. - **Scalability**: Utilizes Docker Compose to efficiently manage and scale the services. **Example Structure:** rag-api-template/ ├── backend/ │ ├── Dockerfile │ ├── app/ │ │ ├── main.py │ │ ├── models/ │ │ └── utils/ ├── frontend/ │ ├── Dockerfile │ ├── src/ │ │ ├── App.tsx │ │ ├── components/ │ │ └── styles/ ├── nginx/ │ ├── nginx.conf ├── docker-compose.yml └── .env I would love to hear feedback and suggestions from the maintainers and the community on this proposal.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#706
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?