wehub-resource-sync
fed8b2eed7
Build and push multi-arch DocsGPT Docker image / build (linux/amd64, ubuntu-latest, amd64) (push) Has been cancelled
Backend release / release (push) Has been cancelled
Bandit Security Scan / bandit_scan (push) Has been cancelled
Build and push multi-arch DocsGPT Docker image / build (linux/arm64, ubuntu-24.04-arm, arm64) (push) Has been cancelled
Build and push multi-arch DocsGPT Docker image / manifest (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / build (linux/amd64, ubuntu-latest, amd64) (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / build (linux/arm64, ubuntu-24.04-arm, arm64) (push) Has been cancelled
Build and push DocsGPT FE Docker image for development / manifest (push) Has been cancelled
Python linting / ruff (push) Has been cancelled
Run python tests with pytest / Run tests and count coverage (3.12) (push) Has been cancelled
React Widget Build / build (push) Has been cancelled
61 lines
1.9 KiB
Markdown
61 lines
1.9 KiB
Markdown
# Welcome to DocsGPT Devcontainer
|
|
|
|
Welcome to the DocsGPT development environment! This guide will help you get started quickly.
|
|
|
|
## Starting Services
|
|
|
|
To run DocsGPT, you need to start three main services: Flask (backend), Celery (task queue), and Vite (frontend). Here are the commands to start each service within the devcontainer:
|
|
|
|
### Vite (Frontend)
|
|
|
|
```bash
|
|
cd frontend
|
|
npm run dev -- --host
|
|
```
|
|
|
|
### Backend (ASGI)
|
|
|
|
Run the full app under uvicorn (serves `/mcp` and the async SSE reconnect
|
|
routes, and matches production):
|
|
|
|
```bash
|
|
uvicorn application.asgi:asgi_app --host 0.0.0.0 --port 7091 --reload
|
|
```
|
|
|
|
`flask --app application/app.py run --host=0.0.0.0 --port=7091` is faster but
|
|
serves only the WSGI Flask app — it omits `/mcp` and the reconnect reader
|
|
`GET /api/messages/<id>/events`, so a dropped stream won't auto-resume.
|
|
|
|
### Celery (Task Queue)
|
|
|
|
```bash
|
|
celery -A application.app.celery worker -l INFO -Q docsgpt,parsing
|
|
```
|
|
|
|
The `parsing` queue serves document parsing (the `read_document` tool / workflow
|
|
native-file parse); without it those calls hang `DOCUMENT_PARSE_TIMEOUT` then
|
|
error. A dedicated `-Q parsing` worker can be GPU-enabled for heavier parsers.
|
|
|
|
## Github Codespaces Instructions
|
|
|
|
### 1. Make Ports Public:
|
|
|
|
Go to the "Ports" panel in Codespaces (usually located at the bottom of the VS Code window).
|
|
|
|
For both port 5173 and 7091, right-click on the port and select "Make Public".
|
|
|
|
|
|
|
|
|
|
### 2. Update VITE_API_HOST:
|
|
|
|
After making port 7091 public, copy the public URL provided by Codespaces for port 7091.
|
|
|
|
Open the file frontend/.env.development.
|
|
|
|
Find the line VITE_API_HOST=http://localhost:7091.
|
|
|
|
Replace http://localhost:7091 with the public URL you copied from Codespaces.
|
|
|
|
|