Update configuration examples to use env(string:) syntax

- Update DFS configuration in clustering.md
- Update Solr configuration examples in install_solr.md
- Align with changes from ibexa/recipes-dev#222

Author: mnocon

docs/ibexa_cloud/environment_variables.md

@@ -5,7 +5,8 @@ description: Environment variables automatically generated by Ibexa Cloud based
 # Environment variables on Ibexa Cloud
 
 [[= product_name_cloud =]] automatically generates environment variables based on the Platform.sh relationships and routes configuration.
-The system parses `PLATFORM_RELATIONSHIPS` and `PLATFORM_ROUTES` environment variables and exposes them as application-specific variables.
+It parses `PLATFORM_RELATIONSHIPS` and `PLATFORM_ROUTES` environment variables and exposes them as application-specific variables.
+Environment variable names are created by converting relationship names to uppercase and replacing hyphens with underscores.
 
 ## Database variables
 
@@ -20,12 +21,12 @@ For MySQL and PostgreSQL databases, the following variables are generated based
 - `{RELATIONSHIP_NAME}_DRIVER` - database driver
 - `{RELATIONSHIP_NAME}_SERVER` - database server
 
-Example: A relationship named `database` generates `DATABASE_URL`, `DATABASE_HOST`, `DATABASE_USER`, etc.
+For example, for a relationship called `database` the environment variables are named `DATABASE_URL`, `DATABASE_HOST`, `DATABASE_USER`, etc.
 
 ## DFS database variables
 
-For distributed file storage (DFS) using a separate database, use the relationship name `dfs_database` (required).
-This generates the standard database variables listed above, plus additional DFS-specific variables when `PLATFORMSH_DFS_NFS_PATH` is set:
+When using [distributed file storage (DFS) using a separate database](clustering.md#dfs-io-handler), you must use the relationship name `dfs_database`.
+In addition to the database variables listed above, additional DFS-specific variables are created when `PLATFORMSH_DFS_NFS_PATH` is set:
 
 - `DFS_NFS_PATH` - NFS path for DFS storage
 - `DFS_DATABASE_CHARSET` - database character set
@@ -98,4 +99,3 @@ Use the following relationship names in `.platform.app.yaml`:
 - `elasticsearch` - Elasticsearch search service
 - `solr` - Solr search service
 
-Environment variable names are derived from relationship names by converting to uppercase and replacing hyphens with underscores.

docs/infrastructure_and_maintenance/clustering/clustering.md

@@ -143,10 +143,9 @@ This example uses Doctrine connection named `dfs`:
 ``` yaml
 parameters:
     env(DFS_DATABASE_URL): '%env(resolve:DATABASE_URL)%'
-    dfs_nfs_path: '%env(resolve:DFS_NFS_PATH)%'
     dfs_database_url: '%env(resolve:DFS_DATABASE_URL)%'
     ibexa.io.nfs.adapter.config:
-        root: '%dfs_nfs_path%'
+        root: '%kernel.project_dir%/%env(string:DFS_NFS_PATH)%'
         path: '$var_dir$/$storage_dir$/'
         writeFlags: ~
         linkHandling: ~
@@ -158,12 +157,12 @@ doctrine:
         connections:
             dfs:
                 # configure these for your database server
-                driver: '%dfs_database_driver%'
-                charset: '%dfs_database_charset%'
+                driver: '%env(string:DFS_DATABASE_DRIVER)%'
+                charset: '%env(string:DFS_DATABASE_CHARSET)%'
                 default_table_options:
-                    charset: '%dfs_database_charset%'
-                    collate: '%dfs_database_collation%'
-                url: '%dfs_database_url%'
+                    charset: '%env(string:DFS_DATABASE_CHARSET)%'
+                    collate: '%env(string:DFS_DATABASE_COLLATION)%'
+                url: '%env(string:DFS_DATABASE_URL)%'
 
 # define the Flysystem handler
 oneup_flysystem:

docs/release_notes/ibexa_dxp_v5.0.md

@@ -10,6 +10,25 @@ month_change: true
 
 <div class="release-notes" markdown="1">
 
+[[% set version = 'v5.0.5' %]]
+
+[[= release_note_entry_begin("Ibexa DXP " + version, '2025-XX-XX', ['Headless', 'Experience', 'Commerce', 'New feature']) =]]
+
+#### Ibexa Cloud improvements
+
+##### New cloud configuration package
+
+A new `ibexa/cloud` package is now available for [[= product_name_cloud =]] deployments.
+This package replaces the previous `composer ibexa:setup --platformsh` command with a dedicated console command.
+
+The package automatically generates environment variables based on Platform.sh relationships and routes configuration, making it easier to configure services like databases, cache, search engines, and session storage.
+
+For more information, see [Install on Ibexa Cloud](install_on_ibexa_cloud.md) and [Environment variables on Ibexa Cloud](environment_variables.md).
+
+[[% include 'snippets/release_50.md' %]]
+
+[[= release_note_entry_end() =]]
+
 [[% set version = 'v5.0.4' %]]
 
 [[= release_note_entry_begin("Integrated help " + version, '2025-12-10', ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature']) =]]

docs/search/search_engines/solr_search_engine/install_solr.md

@@ -183,8 +183,8 @@ Out of the box in [[= product_name =]] the following is enabled for a setup:
 ibexa_solr:
     endpoints:
         endpoint0:
-            dsn: '%solr_dsn%'
-            core: '%solr_core%'
+            dsn: '%env(string:SOLR_DSN)%'
+            core: '%env(string:SOLR_CORE)%'
     connections:
         default:
             entry_endpoints:
@@ -202,10 +202,10 @@ The installation contains several similar languages, and one different language
 ibexa_solr:
     endpoints:
         endpoint0:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core0
         endpoint1:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core1
     connections:
         default:
@@ -232,25 +232,25 @@ ibexa_solr:
     version: '9.8.1' # Required only if using Solr 9
     endpoints:
         endpoint0:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core0
         endpoint1:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core1
         endpoint2:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core2
         endpoint3:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core3
         endpoint4:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core4
         endpoint5:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core5
         endpoint6:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core6
     connections:
         default:
@@ -286,14 +286,14 @@ The example is based on multi-core setup so any specific language analysis optio
 ibexa_solr:
     endpoints:
         main:
-            dsn: '%solr_dsn%'
-            core: '%solr_main_core%'
+            dsn: '%env(string:SOLR_DSN)%'
+            core: '%env(string:SOLR_MAIN_CORE)%'
         en:
-            dsn: '%solr_dsn%'
-            core: '%solr_en_core%'
+            dsn: '%env(string:SOLR_DSN)%'
+            core: '%env(string:SOLR_EN_CORE)%'
         fr:
-            dsn: '%solr_dsn%'
-            core: '%solr_fr_core%'
+            dsn: '%env(string:SOLR_DSN)%'
+            core: '%env(string:SOLR_FR_CORE)%'
         # ...
     connections:
         default:
@@ -325,7 +325,7 @@ In the example below we configured Solr Bundle to work with secured Solr core.
 ibexa_solr:
     endpoints:
         endpoint0:
-            dsn: '%solr_dsn%'
+            dsn: '%env(string:SOLR_DSN)%'
             core: core0
             user: example
             pass: password