mirror of
https://github.com/tiennm99/DocsGPT.git
synced 2026-10-15 04:17:56 +00:00
Alex
574f96341e
The backend import package is now docsgpt, the name it will carry on PyPI; application was far too generic to install into anyone's site-packages. git mv plus a mechanical rewrite of every import, dotted string and path reference: 734 Python files, the compose files, Dockerfile, workflows, docs, setup scripts, devcontainer, k8s manifests, vscode config, pytest and coverage config, .gitignore. Behaviour is unchanged. Kept for one release: - A top-level application package whose meta-path finder resolves application.x.y to the already-imported docsgpt.x.y object, so old imports and entry points (celery -A application.app.celery, uvicorn application.asgi:asgi_app) keep working with a FutureWarning. - Celery registers every application.* task name as an alias of its docsgpt.* task on start-up, so messages queued by the previous release still run. The redbeat key prefix moves to redbeat:docsgpt:v2: so schedule entries the previous release wrote are left unread instead of firing twice. The backend image builds from the repository root (docker build -f docsgpt/Dockerfile .) so it can ship the alias package; a root .dockerignore allow-lists docsgpt/ and application/ and keeps caches, local data, .env files, the sample index files and the Dockerfile out. Compose and the image workflows point at the new context.
12 lines
499 B
Python
12 lines
499 B
Python
"""Repositories for the user-data Postgres database.
|
|
|
|
Each module in this package exposes exactly one repository class. Repository
|
|
methods take a ``Connection`` (either as a constructor argument or as a
|
|
method argument) and return plain ``dict`` rows via
|
|
``docsgpt.storage.db.base_repository.row_to_dict`` during the
|
|
MongoDB→Postgres cutover, so call sites don't have to change shape.
|
|
|
|
Repositories are added one collection at a time, matching the phased
|
|
rollout in ``migration-postgres.md``.
|
|
"""
|