✨ Webdav connector to the Twake Drive

Documentation/docs/internal-documentation/backend-services/documents/database-models.md

@@ -25,6 +25,7 @@ export class DriveFile {
   size: number;
   last_version_cache: Partial<FileVersion>;
   scope: DriveScope;
+  locks: DriveLock[];
 }
 
 type AccessInformation = {
@@ -87,3 +88,21 @@ type DriveFileThumbnail = {
   full_url?: string;
 };
 ```
+
+**DriveLock**
+```Typescript
+export class DriveLock {
+  company_id: string;
+  user_id: string;
+  id: string;
+  drive_file_id: string;
+  token: string;
+  created_at: number;
+  timeout: number;
+  scope: "exclusive" | "shared";
+  depth: "0" | "infinity";
+  provisional: boolean;
+  owner: any;
+  principal: string;
+}
+```

Documentation/docs/internal-documentation/backend-services/webdav/Adapter.md

@@ -0,0 +1,11 @@
+# WebDAV Adapter
+
+The Adapter component serves as the interface between the Nephele WebDAV library and TDrive's file system. It handles resource location, authorization, and provides methods for creating and retrieving resources.
+
+Key features:
+- Implements the `Adapter` interface from Nephele
+- Manages URL to file path conversion
+- Handles authorization checks
+- Creates and retrieves `ResourceService` instances
+
+For implementation details, refer to `Adapter.ts`.

Documentation/docs/internal-documentation/backend-services/webdav/DriveLock.md

@@ -0,0 +1,10 @@
+# DriveLock
+
+The DriveLock component implements locking mechanisms for WebDAV resources in TDrive.
+
+Key features:
+- Creation and management of exclusive and shared locks
+- Lock timeout handling
+- Integration with TDrive's file structure for lock storage
+
+For implementation details, refer to `DriveLock.ts`.

Documentation/docs/internal-documentation/backend-services/webdav/PropertiesService.md

@@ -0,0 +1,10 @@
+# PropertiesService
+
+The PropertiesService manages WebDAV properties for resources in TDrive's file system.
+
+Key features:
+- Retrieval of standard WebDAV properties (e.g., creationdate, displayname, getcontentlength)
+- Custom property management
+- Property listing and modification
+
+For implementation details, refer to `Properties.ts`.

Documentation/docs/internal-documentation/backend-services/webdav/README.md

@@ -0,0 +1,59 @@
+# WebDAV Service for TDrive
+
+This document provides an overview of the WebDAV service implementation for TDrive, which allows users to access and manipulate their files using the WebDAV protocol.
+
+## Table of Contents
+
+1. [Overview](#overview)
+2. [Components](#components)
+3. [Setup and Configuration](#setup-and-configuration)
+4. [Usage](#usage)
+5. [Authentication](#authentication)
+6. [Limitations and Considerations](#limitations-and-considerations)
+
+## Overview
+
+The WebDAV service is implemented using the Nephele library and integrates with TDrive's existing file storage and permission system. It provides standard WebDAV functionality, including file operations (read, write, delete), directory listings, and locking mechanisms.
+
+## Components
+
+The WebDAV service consists of several key components:
+
+1. [Adapter](Adapter.md): Interfaces between Nephele and TDrive's file system.
+2. [ResourceService](ResourceService.md): Implements the Resource interface, handling file and directory operations.
+3. [PropertiesService](PropertiesService.md): Manages WebDAV properties for resources.
+4. [DriveLock](DriveLock.md): Implements locking mechanisms for WebDAV resources.
+
+## Setup and Configuration
+
+To set up the WebDAV service:
+
+1. Ensure all dependencies are installed.
+2. Configure the `routes.ts` file to set up the WebDAV endpoint (default: `internal/services/webdav/v1/webdav`).
+
+## Usage
+
+Once set up, users can connect to the WebDAV service using any WebDAV-compatible client. The service supports standard WebDAV operations such as:
+
+- Browsing directories
+- Uploading and downloading files
+- Creating and deleting directories
+- Moving and copying files/directories
+- Setting and retrieving file properties
+- Locking and unlocking resources
+
+## Authentication
+
+The service uses Basic Authentication. Users need to provide their device ID as the username and device password as the password.
+
+Example:
+```
+Authorization: Basic base64(device_id:device_password)
+```
+
+## Limitations and Considerations
+
+- Locks are stored within the DriveFile object to maintain database compatibility.
+- Performance may vary depending on the size and number of files being accessed.
+
+For more detailed information on each component, please refer to their respective documentation files.

Documentation/docs/internal-documentation/backend-services/webdav/ResourceService.md

@@ -0,0 +1,12 @@
+# ResourceService
+
+The ResourceService implements the `Resource` interface from Nephele, providing methods for file and directory operations within TDrive's file system.
+
+Key features:
+- File and directory CRUD operations
+- Stream handling for file content
+- Lock management
+- Property management
+- Internal member (child resource) handling
+
+For implementation details, refer to `fileResource.ts`.

tdrive/backend/node/config/default.json

@@ -237,6 +237,7 @@
     "documents",
     "applications",
     "applications-api",
-    "tags"
+    "tags",
+    "webdav"
   ]
 }