Merge branch '91-add-required-version-for-docker-server-to-docs' into 'dux'

Subproject commit c2aabf7c72f172666630ae9bba275aa300798cf2

Subproject commit 88b86aefdc5752b6a42713fdbcac4d6451b39b33

### Software Requirements

- Linux operating system: Debian 11 or 12 is recommended

- [Docker Engine](https://docs.docker.com/engine/install/)

- [Docker Engine](https://docs.docker.com/engine/install/) with required version

    v25.0.0 or later

- [Docker Compose](https://docs.docker.com/compose/install/linux/) with

    recommended version v2.27.0

If you encounter issues during deployment, consider the following steps:

- **Executable Permissions**: Ensure that the deployment scripts have executable

    permissions. Run the following command to set the appropriate permissions:

- **Executable Permissions**:

    Ensure that the deployment scripts have executable permissions.

    Run the following command to set the appropriate permissions:

    ```

    chmod +x deploy.sh 01-substitute-env.sh

    chmod +x deploy-with-https.sh generate-cert.sh  # If using HTTPS deployment

    ```

- **INJECT_DOMAIN Setting**: Verify that the INJECT_DOMAIN environment variable

    is set to a domain name and not a static IP address. The platform requires a

    domain name to function correctly. For local test deployments please use

    reserved TLD `.localhost` (example: `inject.localhost`)

- **INJECT_DOMAIN Setting**:

    Verify that the INJECT_DOMAIN environment variable is set to a domain name and not a static IP address.

    The platform requires a domain name to function correctly.

    For local test deployments please use reserved TLD `.localhost` (example: `inject.localhost`)

- **Backend is not returning any valid response**: Verify that the

    `INJECT_DOMAIN` and `INJECT_HOST_ADDRESSES` is set up correctly. The platform

    requires that the addresses are set up to hostnames where the platform is

- **Backend is not returning any valid response**:

    Verify that the `INJECT_DOMAIN` and `INJECT_HOST_ADDRESSES` is set up correctly.

    The platform requires that the addresses are set up to hostnames where the platform is

    expected to be accessed from.

- **Frontend's error log in Developer Console is reporting mixed-origin

    connection issues**: Verify that connection settings in the environment

    variables are set up correctly. If using HTTP deployment, that they use

    `http://` and `ws://` protocol, and when using HTTPS, then `https://` and

    `wss://`.

- **Frontend's error log in Developer Console is reporting mixed-origin connection issues**:

    Verify that connection settings in the environment variables are set up correctly.

    If using HTTP deployment, that they use `http://` and `ws://` protocol, and when using HTTPS,

    then `https://` and `wss://`.

- **Application is connecting to an incorrect backend instance**: Clean up your

    browser local storage to enforce rebinding of the Frontend client.

- **Application is connecting to an incorrect backend instance**:

    Clean up your browser local storage to enforce rebinding of the Frontend client.

- **The application shows an error about frontend and backend versions not being

    compatible**: This usually happens after upgrading to a new version of the

    platform. To resolve this, clear your browser's cache to ensure that the

    frontend loads the latest version and can properly communicate with the

    backend.

- **The application shows an error about frontend and backend versions not being compatible**:

    This usually happens after upgrading to a new version of the platform.

    To resolve this, clear your browser's cache to ensure that the frontend loads

    the latest version and can properly communicate with the backend.

<div class="navigation" markdown>

  [← Installation overview](./overview.md){ .md-button }