FiloraFS-Prov2
FiloraFS-Pro overview
Understand FiloraFS-Pro v2 ownership, storage providers, runtime administration, temporary access, and identity boundary.
Updated
Release baseline
| Item | Value |
|---|---|
| Version | v2 |
| Java | 25 |
| Spring Boot | 4.1.1 |
| Local database | In-memory H2 |
| Persistent database | MySQL 8+ |
| Schema | Flyway migrations; Hibernate validate |
| Storage | LOCAL, AWS S3, and S3-compatible providers such as MinIO |
| License | BuildBaseKit Commercial License |
What FiloraFS-Pro is
FiloraFS-Pro v2 is a paid Spring Boot file-management boilerplate built as a production-ready foundation. It combines authenticated user ownership, persisted file metadata, LOCAL and S3-compatible storage, runtime storage administration, temporary access, and thumbnails.
Identity and file boundary
- Registration, password login, JWT access, rotating refresh credentials, current-session logout, and /api/users/me
- ROLE_USER and ROLE_ADMIN authorization
- Authenticated upload with the uploader persisted as owner
- Owner-scoped list, metadata, inline stream, attachment download, temporary access, thumbnail, and delete operations
- Administrator file access across users without weakening normal cross-user isolation
Storage boundary
- LOCAL is the zero-configuration default.
- AWS S3, MinIO, and compatible S3 implementations use database-backed runtime configuration.
- ROLE_ADMIN saves configuration, tests connectivity, and explicitly switches the provider; saving settings never activates it.
- The active provider controls new uploads. Each file retains its original provider for later reads and deletes.
- If active S3 is unavailable, the operation fails instead of silently writing to LOCAL.
- S3 access and secret keys are encrypted at rest and never returned by the configuration API.
Developer experience
- Maven wrapper startup with no required .env file
- H2 first run and MySQL support
- Flyway-managed schema
- Responsive /api-test browser workbench
- Postman collection
- Automated authentication, authorization, file, storage, temporary-access, thumbnail, migration, and operational tests
- Public Actuator health and info endpoints
Application responsibilities
- Supply stable JWT and storage master keys outside source control.
- Use persistent database and storage, backups, HTTPS, monitoring, and edge rate limits for deployment.
- Add application-specific quotas, retention, and malware scanning when required; malware scanning is not included.
- Review the in-memory S3 read path before using it for large objects.