Alex fe68fec69e feat: docsgpt backup and docsgpt restore ...

`docsgpt backup` writes one archive holding a pg_dump of the database, a tar
of each data volume and a manifest of what it came from; `docsgpt restore`
puts it back over an install. The settings file is left out unless
--with-settings asks for it, since it holds the install's secrets, and a
backup taken with a newer DocsGPT is refused without --force.

The volume tars go through the image the install already runs, so a backup
pulls nothing extra, and compose calls can now redirect stdout and stdin so
the dump never passes through this process.

2026-09-16 21:33:33 +01:00

..

__init__.py

feat: docsgpt up runs and manages DocsGPT on Docker

2026-09-15 22:57:00 +01:00

test_backup.py

feat: docsgpt backup and docsgpt restore

2026-09-16 21:33:33 +01:00

test_commands.py

feat: docsgpt backup and docsgpt restore

2026-09-16 21:33:33 +01:00

test_docker.py

feat: docsgpt backup and docsgpt restore

2026-09-16 21:33:33 +01:00

test_envfile.py

fix: tighten an existing .env to 0600 before rewriting it; CI checks secrets have values

2026-09-16 00:11:38 +01:00

test_stack.py

feat: docsgpt up runs and manages DocsGPT on Docker

2026-09-15 22:57:00 +01:00