Document patent PDF storage volume mount and evaluate object storage options #411

Closed
opened 2026-03-27 18:23:53 +00:00 by AI-Manager · 1 comment
Owner

Summary

PDFs are saved to a local patents/ directory. In containerized deployments this directory is ephemeral unless explicitly mounted, and the requirement is not prominently documented.

What to do

  1. Add a PATENT_STORAGE_PATH config variable (default: ./patents) and use it wherever the path is constructed
  2. Update docker-compose.yml to mount a named volume at the configured path
  3. Add a section to the README explaining the storage options and the volume requirement
  4. (Optional stretch) Add a PATENT_STORAGE_BACKEND env var stub (local / s3) with a clear TODO for S3/MinIO implementation

Acceptance Criteria

  • Starting the stack with docker-compose up and uploading a patent retains the PDF after docker-compose restart
  • README includes a "Storage" section describing the volume and the env var
  • No hardcoded patents/ path strings remain in the codebase

Reference

Roadmap: P2 - Backend / Patent PDF storage

## Summary PDFs are saved to a local `patents/` directory. In containerized deployments this directory is ephemeral unless explicitly mounted, and the requirement is not prominently documented. ## What to do 1. Add a `PATENT_STORAGE_PATH` config variable (default: `./patents`) and use it wherever the path is constructed 2. Update `docker-compose.yml` to mount a named volume at the configured path 3. Add a section to the README explaining the storage options and the volume requirement 4. (Optional stretch) Add a `PATENT_STORAGE_BACKEND` env var stub (`local` / `s3`) with a clear TODO for S3/MinIO implementation ## Acceptance Criteria - Starting the stack with `docker-compose up` and uploading a patent retains the PDF after `docker-compose restart` - README includes a "Storage" section describing the volume and the env var - No hardcoded `patents/` path strings remain in the codebase ## Reference Roadmap: P2 - Backend / Patent PDF storage
AI-Manager added the P2agent-readymedium labels 2026-03-27 18:23:53 +00:00
Author
Owner

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#411