leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Document patent PDF storage volume mount and consider object storage path #621

New Issue
Closed
opened 2026-03-28 11:22:29 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:22:29 +00:00
Owner
Copy Link
Copy Source

Context

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

Roadmap item: P2 > Backend > Patent PDF storage

What to do

  • Add a named volume for patents/ in docker-compose.yml and document it in the README.
  • In a follow-up (separate issue), evaluate object storage (S3/MinIO) as a longer-term solution — note this as a future improvement in the docs.
  • Alternatively, if the team decides to move to object storage now, implement a MinIO-backed storage abstraction behind an interface so the backend is storage-agnostic.

For this issue, the minimum deliverable is the volume mount documentation.

Acceptance criteria

  • docker-compose.yml declares a named volume for the patents/ path.
  • README describes the volume mount and explains that PDFs are persisted there.
  • A comment in the compose file links to the future object storage issue.
## Context PDFs are written to a local `patents/` directory. In containerized deployments this directory is ephemeral unless a volume is explicitly mounted, and the requirement is not documented. Roadmap item: P2 > Backend > Patent PDF storage ## What to do - Add a named volume for `patents/` in `docker-compose.yml` and document it in the README. - In a follow-up (separate issue), evaluate object storage (S3/MinIO) as a longer-term solution — note this as a future improvement in the docs. - Alternatively, if the team decides to move to object storage now, implement a MinIO-backed storage abstraction behind an interface so the backend is storage-agnostic. For this issue, the minimum deliverable is the volume mount documentation. ## Acceptance criteria - [ ] `docker-compose.yml` declares a named volume for the `patents/` path. - [ ] README describes the volume mount and explains that PDFs are persisted there. - [ ] A comment in the compose file links to the future object storage issue.
AI-Manager added the P2agent-readysmallinfra labels 2026-03-28 11:22:29 +00:00
AI-Manager commented 2026-03-28 12:04:35 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. docker-compose.yml mounts ./patents:/app/patents for local storage and includes an optional MinIO/S3 service (enabled via STORAGE_BACKEND=s3). config.py has S3 configuration variables.

Closing: already implemented on main. `docker-compose.yml` mounts `./patents:/app/patents` for local storage and includes an optional MinIO/S3 service (enabled via `STORAGE_BACKEND=s3`). `config.py` has S3 configuration variables.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready infra small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#621
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?