Feature/improve entity files endpoints

docs/backend/EXTENSIONS.md

@@ -301,6 +301,16 @@ dynamia.entityfiles.s3.secret-key=${AWS_SECRET_KEY}
 ```
 
 ### When to Use Entity Files Extension
+#### MinIO Storage
+```properties
+# MinIO storage
+DEFAULT_STORAGE_ID=MinioStorage
+MINIO_ENDPOINT=http://localhost:9000
+MINIO_BUCKET=my-bucket
+MINIO_REGION=us-east-1
+MINIO_ACCESS_KEY=${MINIO_ACCESS_KEY}
+MINIO_SECRET_KEY=${MINIO_SECRET_KEY}
+```
 
 - Attach documents to records
 - Store user profiles or avatars

examples/demo-zk-books/pom.xml

@@ -32,7 +32,7 @@
     <parent>
         <groupId>org.springframework.boot</groupId>
         <artifactId>spring-boot-starter-parent</artifactId>
-        <version>4.0.3</version>
+        <version>4.0.6</version>
         <relativePath/> <!-- lookup parent from repository -->
     </parent>
 
@@ -47,7 +47,7 @@
         <timestamp>${maven.build.timestamp}</timestamp>
         <maven.build.timestamp.format>yyyyMMdd</maven.build.timestamp.format>
 
-        <tools.version>26.4.0</tools.version>
+        <tools.version>26.5.0</tools.version>
 
     </properties>
 

extensions/dashboard/sources/pom.xml

@@ -23,7 +23,7 @@
     <parent>
         <groupId>tools.dynamia.modules</groupId>
         <artifactId>tools.dynamia.modules.parent</artifactId>
-        <version>26.4.1</version>
+        <version>26.5.0</version>
         <relativePath>../../pom.xml</relativePath>
     </parent>
 
@@ -38,12 +38,12 @@
         <dependency>
             <groupId>tools.dynamia</groupId>
             <artifactId>tools.dynamia.zk</artifactId>
-            <version>26.4.1</version>
+            <version>26.5.0</version>
         </dependency>
         <dependency>
             <groupId>tools.dynamia.modules</groupId>
             <artifactId>tools.dynamia.modules.saas.api</artifactId>
-            <version>26.4.1</version>
+            <version>26.5.0</version>
         </dependency>
     </dependencies>
 

extensions/email-sms/sources/core/pom.xml

@@ -23,7 +23,7 @@
     <parent>
         <artifactId>tools.dynamia.modules.email.parent</artifactId>
         <groupId>tools.dynamia.modules</groupId>
-        <version>26.4.1</version>
+        <version>26.5.0</version>
     </parent>
 
     <artifactId>tools.dynamia.modules.email</artifactId>
@@ -50,12 +50,12 @@
         <dependency>
             <groupId>tools.dynamia</groupId>
             <artifactId>tools.dynamia.domain.jpa</artifactId>
-            <version>26.4.1</version>
+            <version>26.5.0</version>
         </dependency>
         <dependency>
             <groupId>tools.dynamia</groupId>
             <artifactId>tools.dynamia.templates</artifactId>
-            <version>26.4.1</version>
+            <version>26.5.0</version>
         </dependency>
         <dependency>
             <groupId>org.springframework</groupId>

extensions/email-sms/sources/pom.xml

@@ -23,7 +23,7 @@
     <parent>
         <groupId>tools.dynamia.modules</groupId>
         <artifactId>tools.dynamia.modules.parent</artifactId>
-        <version>26.4.1</version>
+        <version>26.5.0</version>
         <relativePath>../../pom.xml</relativePath>
     </parent>
 
@@ -85,7 +85,7 @@
         <dependency>
             <groupId>tools.dynamia.modules</groupId>
             <artifactId>tools.dynamia.modules.saas.jpa</artifactId>
-            <version>26.4.1</version>
+            <version>26.5.0</version>
         </dependency>
 
 

extensions/email-sms/sources/ui/pom.xml

@@ -22,7 +22,7 @@
 	<parent>
 		<artifactId>tools.dynamia.modules.email.parent</artifactId>
 		<groupId>tools.dynamia.modules</groupId>
-		<version>26.4.1</version>
+		<version>26.5.0</version>
 	</parent>
 
 	<name>DynamiaModules - Email UI</name>
@@ -34,12 +34,12 @@
 		<dependency>
 			<groupId>tools.dynamia</groupId>
 			<artifactId>tools.dynamia.zk</artifactId>
-			<version>26.4.1</version>
+			<version>26.5.0</version>
 		</dependency>
 		<dependency>
 			<groupId>tools.dynamia.modules</groupId>
 			<artifactId>tools.dynamia.modules.email</artifactId>
-			<version>26.4.1</version>
+			<version>26.5.0</version>
 		</dependency>
 		<dependency>
 			<groupId>tools.dynamia.zk.addons</groupId>

extensions/entity-files/README.md

@@ -43,12 +43,22 @@ metadata are store in the database in table `mod_entity_files` using JPA entity
     </dependency>
 ```
 
+#### MinIO Support
+```xml
+    <dependency>
+        <groupId>tools.dynamia.modules</groupId>
+        <artifactId>tools.dynamia.modules.entityfiles.minio</artifactId>
+        <version>7.4.0</version>
+    </dependency>
+```
+
 ### Gradle
 
 ```groovy
 compile 'tools.dynamia.modules:tools.dynamia.modules.entityfiles:7.4.0'
 compile 'tools.dynamia.modules:tools.dynamia.modules.entityfiles.ui:7.4.0'
 compile 'tools.dynamia.modules:tools.dynamia.modules.entityfiles.s3:7.4.0'
+compile 'tools.dynamia.modules:tools.dynamia.modules.entityfiles.minio:7.4.0'
 ```
 
 ## Usage
@@ -115,6 +125,7 @@ files.
 
 - `LocalEntityFileStorage` is the default implementation and store files in local file system
 - `S3EntityFileStorage` in module S3 can upload files to AWS S3 buckets
+- `MinioEntityFileStorage` in module MinIO can upload files to MinIO buckets using the MinIO Java SDK
 
 ## License
 

extensions/entity-files/packages/files-sdk/README.md

@@ -2,9 +2,9 @@
 
 > TypeScript / JavaScript client SDK for the Dynamia Entity Files extension REST API.
 
-`@dynamia-tools/files-sdk` provides a small, focused client to download files managed by the Entity Files extension of a Dynamia Platform backend. The package exposes a single API class, `FilesApi`, which delegates HTTP, authentication and error handling to the core `@dynamia-tools/sdk` `HttpClient`.
+`@dynamia-tools/files-sdk` provides a small, focused client to download, inspect and upload files managed by the Entity Files extension of a Dynamia Platform backend. The package exposes a single API class, `FilesApi`, which delegates base URL handling to the core `@dynamia-tools/sdk` `HttpClient` and reuses the same authentication context for upload operations.
 
-This README explains how to install the package, how to use `FilesApi` (recommended via `DynamiaClient`) and how to handle binary downloads in browser and Node.js environments.
+This README explains how to install the package, how to use `FilesApi` (recommended via `DynamiaClient`) and how to handle downloads plus the new multipart / base64 upload flows.
 
 ---
 
@@ -13,6 +13,7 @@ This README explains how to install the package, how to use `FilesApi` (recommen
 - [Installation](#installation)
 - [Quick Start (recommended)](#quick-start-recommended)
 - [API methods](#api-methods)
+- [Upload examples](#upload-examples)
 - [Browser example (download and show)](#browser-example-download-and-show)
 - [Node.js example (save to disk)](#nodejs-example-save-to-disk)
 - [Authentication & Errors](#authentication--errors)
@@ -54,27 +55,82 @@ const files = new FilesApi(client.http);
 // Download a file as a Blob (browser)
 const blob = await files.download('myfile.pdf', 'f9a3e8c2-...');
 
+// Get file metadata and direct URL from the server
+const metadata = await files.export('f9a3e8c2-...');
+
 // Get a direct URL (no network call performed)
-const url = files.getUrl('images/logo.png', 'f9a3e8c2-...');
+const url = files.getUrl('myfile.pdf', 'f9a3e8c2-...');
 console.log(url);
 ```
 
 Notes:
 - `FilesApi` methods are thin wrappers over the core `HttpClient` (`get`, `url`) implemented by `DynamiaClient`.
-- The `download()` method calls `GET /storage/{file}?uuid={uuid}` and returns a `Blob` in browser environments; when running in Node.js the underlying fetch polyfill may provide an `ArrayBuffer`/`Buffer` which you should convert to a file.
+- The `download()` method calls `GET /storage/{uuid}/{file}` and returns a `Blob` in browser environments; when running in Node.js the underlying fetch polyfill may provide an `ArrayBuffer`/`Buffer` which you should convert to a file.
+- The upload methods call the new REST endpoints exposed by `EntityFileStorageController`: `POST /api/storage/upload` and `POST /api/storage/upload-base64`.
 
 ---
 
 ## API methods
 
-The implementation in `src/api.ts` exposes two methods on `FilesApi`:
+The implementation in `src/api.ts` exposes the following methods on `FilesApi`:
 
+- `export(uuid: string): Promise<EntityFileExportResponse>`
+  - GET `/api/storage/{uuid}/export` — Returns server-side metadata such as `name`, `size`, `version` and `url`.
 - `download(file: string, uuid: string): Promise<Blob>`
-  - GET `/storage/{file}?uuid={uuid}` — Downloads the file. The SDK returns parsed JSON for `application/json` responses and a `Blob` for other content types (binary).
+  - GET `/storage/{uuid}/{file}` — Downloads the file. The SDK returns parsed JSON for `application/json` responses and a `Blob` for other content types (binary).
 - `getUrl(file: string, uuid: string): string`
-  - Returns a fully-qualified URL that points to `/storage/{file}` with the `uuid` query parameter. No HTTP request is made.
+  - Returns a fully-qualified URL that points to `/storage/{uuid}/{file}`. No HTTP request is made.
+- `uploadMultipart(file: Blob | File, options?: MultipartUploadOptions): Promise<EntityFileUploadResponse>`
+  - POST `/api/storage/upload` — Uploads a file using multipart form data.
+- `uploadBase64(request: Base64UploadRequest): Promise<EntityFileUploadResponse>`
+  - POST `/api/storage/upload-base64` — Uploads a file using JSON containing `base64` or `data` content.
+
+Use `download()` when you need the file content programmatically (e.g., for preview or file save). Use `getUrl()` when you want to put a direct link in an `img` `src`, anchor `href`, or let the browser perform the download. Use `export()` when you need server-generated metadata or a pre-authorized URL. Use the upload methods when the frontend must create `EntityFile` records directly.
+
+---
+
+## Upload examples
+
+### Multipart upload
+
+```ts
+const uploaded = await files.uploadMultipart(fileInput.files![0], {
+  className: 'com.example.crm.Customer',
+  entityId: 15,
+  description: 'Signed contract',
+  shared: false,
+  parentUuid: 'folder-uuid',
+});
+
+console.log(uploaded.uuid, uploaded.url);
+```
+
+### Base64 JSON upload
+
+```ts
+const uploaded = await files.uploadBase64({
+  fileName: 'avatar.png',
+  contentType: 'image/png',
+  base64: imageBase64,
+  className: 'com.example.crm.Customer',
+  entityId: '15',
+  shared: true,
+});
+
+console.log(uploaded.uuid, uploaded.valid);
+```
+
+Both upload methods support these optional fields:
+
+- `className`
+- `entityId`
+- `description`
+- `shared`
+- `subfolder`
+- `storedFileName`
+- `parentUuid`
 
-Use `download()` when you need the file content programmatically (e.g., for preview or file save). Use `getUrl()` when you want to put a direct link in an `img` `src`, anchor `href`, or let the browser perform the download.
+When `className` and `entityId` are omitted, the server creates a temporal file. When both are provided, the uploaded file is attached to the referenced entity.
 
 ---
 

extensions/entity-files/packages/files-sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dynamia-tools/files-sdk",
-  "version": "26.4.1",
+  "version": "26.5.0",
   "website": "https://dynamia.tools",
   "description": "TypeScript/JavaScript client SDK for the Dynamia Entity Files extension REST API",
   "keywords": [