chore: add prettier (#374)

* chore: add prettier

* format

* add to ci

* use ;

* use single quotes as its as well docusaurus default

Author: AlexAndBear

.prettierignore

@@ -0,0 +1,12 @@
+*
+
+!*.md
+!*.mdx
+
+!*/
+
+assets/**
+static/**
+README.md
+CHANGELOG.md
+Contributing.md

.woodpecker/build.yaml

@@ -9,6 +9,11 @@ steps:
     image: quay.io/thegeeklab/git-batch
     commands:
       - git batch -vv
+  - name: format-check
+    image: owncloudci/nodejs:20
+    commands:
+      - pnpm install
+      - pnpm format:check
   - name: build
     image: owncloudci/nodejs:20
     commands:

docs/admin/configuration/authentication-and-user-management/external-idp.md

@@ -60,18 +60,18 @@ for an example.
 
 ```yaml
 role_assignment:
-    driver: oidc
-    oidc_role_mapper:
-        role_claim: opencloudRoles
-        role_mapping:
-            - role_name: admin
-              claim_value: myAdminRole
-            - role_name: spaceadmin
-              claim_value: mySpaceAdminRole
-            - role_name: user
-              claim_value: myUserRole
-            - role_name: guest
-              claim_value: myGuestRole
+  driver: oidc
+  oidc_role_mapper:
+    role_claim: opencloudRoles
+    role_mapping:
+      - role_name: admin
+        claim_value: myAdminRole
+      - role_name: spaceadmin
+        claim_value: mySpaceAdminRole
+      - role_name: user
+        claim_value: myUserRole
+      - role_name: guest
+        claim_value: myGuestRole
 ```
 
 This would assign the role `admin` to users with the value `myAdminRole` in the claim `opencloudRoles`.
@@ -115,7 +115,7 @@ The web client is used for browser-based access to OpenCloud:
 
 - **Client ID**: `web`
 - **Client Type**: Public client
-- **Redirect URIs**: 
+- **Redirect URIs**:
   - `https://your-domain.example.com/`
   - `https://your-domain.example.com/oidc-callback.html`
   - `https://your-domain.example.com/oidc-silent-redirect.html`

docs/admin/configuration/authentication-and-user-management/index.md

@@ -6,7 +6,7 @@ title: 'Authentication and Identity Management'
 
 OpenCloud employs a dual-track authentication strategy:
 
-1. **Built-in IDP (Identity Provider)**: 
+1. **Built-in IDP (Identity Provider)**:
    - Based on LibreGraph Connect (lico)
    - Targeted at smaller installations (up to 500 users)
    - Designed for standalone or small deployments

docs/admin/configuration/authentication-and-user-management/keycloak.md

@@ -8,6 +8,7 @@ title: Keycloak Integration
 
 OpenCloud supports using Keycloak as an external identity provider, providing enterprise-grade identity management capabilities. This guide explains how to set up and configure Keycloak with OpenCloud.
 This guide is divided into three main sections:
+
 - **[Keycloak Integration Overview](#opencloud-configuration-for-keycloak-general)**: A brief overview of the integration process.
 - **[Shared User Directory Mode](#configuration-for-shared-directory-mode)**: Keycloak and OpenCloud share a common LDAP directory for user management.
 - **[Autoprovisioning Mode](#configuration-for-autoprovisioning-mode)**: OpenCloud autoprovisions users in a separate LDAP directory managed by OpenCloud.
@@ -50,12 +51,12 @@ If you need to manually configure the clients in Keycloak:
 3. Navigate to Clients and click Create
 4. Configure each client according to the specifications above
 5. Ensure all clients have the appropriate scopes:
-    - web-origins
-    - profile
-    - roles
-    - groups
-    - basic
-    - email
+   - web-origins
+   - profile
+   - roles
+   - groups
+   - basic
+   - email
 
 ### Advanced Configuration
 
@@ -66,7 +67,6 @@ OpenCloud supports Keycloak's backchannel logout feature, which allows Keycloak
 - **Backchannel Logout URL**: `https://your-domain.example.com/backchannel_logout`
 - **Backchannel Logout Session Required**: `true`
 
-
 ## Shared User Directory Mode
 
 ```mermaid
@@ -98,6 +98,7 @@ graph TD
 In this mode, a readable LDAP Directory with existing users serves as a central user directory for both Keycloak and OpenCloud.
 
 **Key characteristics:**
+
 - LDAP is the source of truth for user information
 - The LDAP server uses standard attributes (uid, cn, sn, givenName, mail)
 - A common unique identifier (e.g. `entryUUID` or `objectGUID`) guarantees stable user mapping even if users are changing
@@ -115,6 +116,7 @@ OpenCloud can work with any LDAP schema containing standard attributes:
 - Default configuration sets LDAP as read-only
 
 **Example LDAP Structure:**
+
 ```bash
 dc=example,dc=org              # Base DN
 ├── ou=users                   # User organizational unit
@@ -184,6 +186,7 @@ OpenCloud provides complete example deployments using Docker Compose:
 2. Edit the `.env` file to enable the Shared Directory Mode:
 
 **For Shared Directory Mode:**
+
 ```bash
 # Enable services
 LDAP=:ldap.yml
@@ -202,6 +205,7 @@ Keycloak is configured during startup by importing the `keycloak-realm.dist.json
 Keycloak can import the realm configuration file **only once** during the first startup. If you need to change the configuration, you must delete the Keycloak container and volume and restart it. This will reset Keycloak to its initial state.
 
 :::
+
 ## Autoprovisioning Mode
 
 In this mode, Keycloak is holding all users and OpenCloud autoprovisions new users during first login.
@@ -289,6 +293,7 @@ OpenCloud provides complete example deployments using Docker Compose:
 2. Edit the `.env` file to enable the Autoprovisioning Mode:
 
 **For Autoprovisioning Mode:**
+
 ```bash
 # Enable services
 LDAP=:ldap.yml
@@ -311,8 +316,8 @@ Keycloak can import the realm configuration file **only once** during the first
 
 Common issues and solutions:
 
-- **User cannot log in**: 
-  - Check LDAP connectivity and user existence 
+- **User cannot log in**:
+  - Check LDAP connectivity and user existence
   - Check if each user has an OpenCloud Role assigned
   - Verify that the client IDs and redirect URIs match exactly
 - **Groups not synchronized**: Verify group mappings in Keycloak

docs/admin/configuration/logging.md

@@ -21,18 +21,23 @@ Set the global log level using the `OPEN_CLOUD_LOG_LEVEL` environment variable.
 ## The log levels are:
 
 ### FATAL
+
 Critical issues that cause the application to shut down — such as config errors or missing dependencies.
 
 ### ERROR
+
 Severe problems that block proper operation and require admin attention.
 
 ### WARN
+
 Unexpected conditions that don’t stop the app but may need investigation.
 
 ### INFO
+
 Routine events that confirm expected behavior and operation.
 
 ### DEBUG
+
 Highly detailed messages for diagnosing problems. Use cautiously in production due to verbosity.
 
 ---
@@ -47,3 +52,4 @@ To manually test with `curl`, add:
 
 ```bash
 --header "X-Request-ID: <your-id>"
+```

docs/admin/configuration/mail-notifications.md

@@ -2,7 +2,7 @@
 sidebar_position: 9
 id: mail-notificatons
 title: Mail Notifications
-description: "How to activate mail notifications in OpenCloud."
+description: 'How to activate mail notifications in OpenCloud.'
 ---
 
 # Mail notifications in OpenCloud
@@ -38,7 +38,7 @@ SMTP_USERNAME=YOUR_USERNAME
 SMTP_PASSWORD=YOUR_PASSWORD
 SMTP_TRANSPORT_ENCRYPTION=none
 SMTP_INSECURE=true
-````
+```
 
 ⚠️ In the .env file, values should be written without quotation marks. Do not use 'single quotes' or "double quotes" — just enter the plain value.
 
@@ -55,10 +55,10 @@ For nano, press Ctrl + O to save and Ctrl + X to exit.
 Apply the changes by restarting the OpenCloud services:
 
 ```bash
-docker compose down 
+docker compose down
 docker compose up -d
 ```
 
 ---
 
-OpenCloud is now successfully configured to deliver notification emails, including those triggered by actions such as file sharing.
+OpenCloud is now successfully configured to deliver notification emails, including those triggered by actions such as file sharing.

docs/admin/configuration/radicale-integration.md

@@ -2,7 +2,7 @@
 sidebar_position: 12
 id: radicale-integration
 title: Calendar and Contacts Integration with Radicale
-description: "How to enable Calendar and Contacts integration via Radicale in OpenCloud."
+description: 'How to enable Calendar and Contacts integration via Radicale in OpenCloud.'
 ---
 
 OpenCloud is able to act as an authenticating reverse proxy for the open-source
@@ -13,15 +13,13 @@ used with a wide selection of desktop- and mobile clients without hassle.
 The `opencloud_full` deployment example already contains all the required pieces to
 setup the integration. This guide explains the required steps to achieve that.
 
-
 :::note
 The calendar and contacts feature is - until further notice - intended for
 non-customers, i.e. please note that it is not covered under our business
 license, and we do not provide professional support for it. This means that
 this feature is maintained and supported on best effort without warranty.
 :::
 
-
 ## Setting up Calendar and Contacts Integration with Radicale
 
 To use this feature you need at least OpenCloud Version 2.3.0. Earlier releases lack
@@ -30,7 +28,7 @@ deployment based on the `opencloud_full` deployment example.
 
 ### 1. Configure the `.env` file to deploy Radicale
 
-In the root directory of the `opencloud_full` deployment example, usually `opencloud/deployments/examples/opencloud_full`, 
+In the root directory of the `opencloud_full` deployment example, usually `opencloud/deployments/examples/opencloud_full`,
 remove the `#` symbol from the line:
 
 ```

docs/admin/configuration/storage/cephfs.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 2
 id: storage-cephfs
-title: "CephsFS"
+title: 'CephsFS'
 draft: true
----
+---

docs/admin/configuration/storage/decomposeds3.md

@@ -1,7 +1,7 @@
 ---
 sidebar_position: 3
 id: storage-decomposeds3
-title: "Decomposeds3"
+title: 'Decomposeds3'
 ---
 
 # Decomposeds3 Storage Driver
@@ -11,13 +11,14 @@ Decomposeds3 is a storage driver for OpenCloud that uses MinIO, an S3-compatible
 ---
 
 **Prerequisites:**
+
 - **Linux**, **Mac** or **Windows** Subsystem for Linux [(WSL)](https://learn.microsoft.com/en-us/windows/wsl/install)
 - [**Docker**](https://docs.docker.com/compose/install/)
 - [**Docker Compose**](https://docs.docker.com/compose/install/)
 
 ---
 
-##  1. Download
+## 1. Download
 
 Download the `opencloud_full` folder (this folder contains a multi-file Docker Compose configuration):
 
@@ -49,7 +50,7 @@ docker compose up -d
 
 This starts all necessary containers in the background.
 
-## 3. Add local domains to /etc/hosts 
+## 3. Add local domains to /etc/hosts
 
 Edit the /etc/hosts file and add the following entries for local access:
 
@@ -61,6 +62,7 @@ Edit the /etc/hosts file and add the following entries for local access:
 ## 4. Login
 
 Login with your browser:
+
 - [https://cloud.opencloud.test](https://cloud.opencloud.test)
 - user: **admin**
 - password: **admin**
@@ -71,10 +73,10 @@ Login with your browser:
 
 <img src={require("./../img/decomposeds3-with-minio.png").default} alt="Admin general" width="1920"/>
 
---- 
+---
 
 ### Troubleshooting
 
-If you encounter any issues or errors, try finding a solution here: 
+If you encounter any issues or errors, try finding a solution here:
 
 - [Common Issues & Help](../../resources/common-issues.md)