FiloraFS-Prov1.0.0
FiloraFS-Pro storage
Understand local storage, AWS S3, metadata, file lifecycle, temporary access, and provider limits.
Updated
Provider availability
| Capability | Local | AWS S3 |
|---|---|---|
| Instant-run default | Yes | No |
| Persisted metadata | Yes | Yes |
| Temporary access | Application token | Native pre-signed URL |
| Image thumbnails | Yes | Yes |
Local storage
Local storage is the zero-configuration provider. Files use the configured directory while metadata is persisted separately.
- Set a persistent absolute directory through .env for development.
- Mount persistent storage in container deployments.
- Back up files and metadata together.
- Do not use one local directory across independent stateless instances without coordination.
AWS S3
Enable S3 through .env only after the local flow works. The storage service uses the configured bucket and records the selected provider with each file.
File lifecycle
- Upload validates file size and the content-type allowlist.
- Metadata records identity, content, size, provider, uploader, and time.
- Stream and download resolve the provider from persisted storage type.
- Delete removes the provider object, metadata, and associated thumbnail.
Temporary access
Local files use random application tokens with expiry. S3 files use native pre-signed GET URLs when the presigner is available.
Security and scale limits
- Authentication alone does not guarantee file ownership.
- Large S3 downloads should avoid loading complete objects into application memory.
- Add pagination, quotas, malware scanning, retention, and audit behavior as required.