docs: replace MinIO with filesystem storage throughout #139
Reference in New Issue
Block a user
Delete Branch "update-silo-fs-docs"
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?
Remove all MinIO/S3 references from documentation and deployment configs. Silo now uses local filesystem storage exclusively.
Updated files:
docs/CONFIGURATION.md— storage section now documents filesystem backenddocs/DEPLOYMENT.md— architecture diagram, external services, troubleshootingdocs/INSTALL.md— remove MinIO setup, update architecture diagramsdocs/SPECIFICATION.md— architecture, technology stack, file storage strategydocs/STATUS.md— storage backend statusdocs/GAP_ANALYSIS.md— file handling referencesdocs/ROADMAP.md— file storage appendix entriesdeployments/config.prod.yaml— filesystem backend configdeployments/systemd/silod.env.example— remove MinIO credential varsAlso includes
scripts/migrate-storage.shfor running the MinIO-to-filesystem migration on a remote host via SSH.