Skip to content

Documented ibexa/cloud package#2985

Open
mnocon wants to merge 15 commits into5.0from
ibea-cloud
Open

Documented ibexa/cloud package#2985
mnocon wants to merge 15 commits into5.0from
ibea-cloud

Conversation

@mnocon
Copy link
Contributor

@mnocon mnocon commented Dec 15, 2025

@mnocon mnocon force-pushed the ibea-cloud branch 2 times, most recently from df66a49 to f4bdd53 Compare December 16, 2025 12:23
@mnocon mnocon marked this pull request as ready for review December 16, 2025 12:34
@mnocon mnocon requested review from barw4 and micszo December 16, 2025 12:35

- `database` - main application database
- `dfs_database` - DFS database (required name for DFS functionality)
- `rediscache` - Redis for cache

This comment was marked as resolved.

!!! note "[[= product_name_cloud =]]"

For [[= product_name_cloud =]]/Platform.sh: This is automatically configured in `vendor/ibexa/core/src/bundle/Core/DependencyInjection/IbexaCoreExtension.php` if you have enabled Redis as `rediscache` Platform.sh service.
For [[= product_name_cloud =]]/Platform.sh, it's configured based on the `.platform.app.yaml` file by the [`ibexa/cloud` package](install_on_ibexa_cloud.md).
Copy link
Contributor

@barw4 barw4 Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we migrate naming to "Upsun"?

dsn: '%solr_dsn%'
core: '%solr_main_core%'
dsn: '%env(string:SOLR_DSN)%'
core: '%env(string:SOLR_MAIN_CORE)%'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think *_CORE are not exposed, it's rather *_HOST now, something to be verified

@mnocon
Copy link
Contributor Author

mnocon commented Jan 21, 2026

Thanky you @barw4 , I've added improvements in f8b7e1e

Two questions that came to my mind:

  • Should we still mention Memcached? It's not supported in v5
  • Should we somehow mention Valkey here? We probably should, but is it correctly detected etc.?

@mnocon mnocon requested a review from barw4 January 22, 2026 08:25
@mnocon mnocon added the Wait with merge PRs that shouldn't be merged instantly label Feb 10, 2026
@barw4
Copy link
Contributor

barw4 commented Feb 17, 2026

Should we still mention Memcached? It's not supported in v5

If it's not supported, let's not mention it.

  • Should we somehow mention Valkey here? We probably should, but is it correctly detected etc.?

Yes, we are supporting it and I think @micszo tested it already

@mnocon
Copy link
Contributor Author

mnocon commented Feb 17, 2026

Memcached mentions removed in b286cd9

@mnocon mnocon requested a review from a team February 26, 2026 09:43
@ibexa-workflow-automation-1 ibexa-workflow-automation-1 bot requested review from adriendupuis, dabrt and julitafalcondusza and removed request for a team February 26, 2026 09:43
@sonarqubecloud
Copy link

|[ibexa/i18n](https://github.com/ibexa/i18n)|Centralized translations to ease synchronization with Crowdin|
|[ibexa/notifications](https://github.com/ibexa/notifications)| Sending [notifications](notifications.md)|
|[ibexa/post-install](https://github.com/ibexa/post-install)|Post installation tool|
|[ibexa/cloud](https://github.com/ibexa/cloud)|(Optional) [[= product_name_cloud =]] integration package|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the package is optional, shouldn't it be treates like an LTS update, which by definition are opt-in bundles?

|[ibexa/notifications](https://github.com/ibexa/notifications)| Sending [notifications](notifications.md)|
|[ibexa/post-install](https://github.com/ibexa/post-install)|Post installation tool|
|[ibexa/cloud](https://github.com/ibexa/cloud)|(Optional) [[= product_name_cloud =]] integration package|
|[ibexa/post-install](https://github.com/ibexa/post-install)|Bundle containing Apache and nginx templates|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|[ibexa/post-install](https://github.com/ibexa/post-install)|Bundle containing Apache and nginx templates|
|[ibexa/post-install](https://github.com/ibexa/post-install)|Apache and nginx templates|


# Environment variables on Ibexa Cloud

[[= product_name_cloud =]] automatically generates environment variables based on the Upsun relationships and routes configuration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[[= product_name_cloud =]] automatically generates environment variables based on the Upsun relationships and routes configuration.
[[= product_name_cloud =]] automatically generates environment variables based on the Upsun relationship and route configuration.

Is it "configuration of relationships and routes" or "relationships and configurations of routes"?


Environment variable prefixes are created by converting relationship names to uppercase and replacing hyphens with underscores.

When multiple endpoints are defined for a single relationship, numerical indices are used for all entries except the first one, for example: `SOLR`, `SOLR_1_`, `SOLR_2`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be SOLR_1_ or SOLR_1 ?


## Environment variables in configuration files

If you're referencing [[= product_name_cloud =]] environment variables in your configuration files, you must define placeholder values for them in your `.env` file to prevent Symfony container initialization failures.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this call for a warning?, if yes, I'd put "To prevent..." first, followed by "you must define"

!!! note "[[= product_name_cloud =]]"

For [[= product_name_cloud =]]: This is automatically configured in `vendor/ibexa/core/src/bundle/Core/DependencyInjection/IbexaCoreExtension.php` if you have enabled Redis as `rediscache` Upsun service.
For [[= product_name_cloud =]], it's configured based on the `.platform.app.yaml` file by the [`ibexa/cloud` package](install_on_ibexa_cloud.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For [[= product_name_cloud =]], it's configured based on the `.platform.app.yaml` file by the [`ibexa/cloud` package](install_on_ibexa_cloud.md).
For [[= product_name_cloud =]] installations, the [`ibexa/cloud` package](install_on_ibexa_cloud.md) performs configuration based on the `.platform.app.yaml` file.

!!! note "[[= product_name_cloud =]]"

For [[= product_name_cloud =]], this is already configured based on `.platform.app.yaml` config.
For [[= product_name_cloud =]], it's configured based on the `.platform.app.yaml` file by the [`ibexa/cloud` package](install_on_ibexa_cloud.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For [[= product_name_cloud =]], it's configured based on the `.platform.app.yaml` file by the [`ibexa/cloud` package](install_on_ibexa_cloud.md).
For [[= product_name_cloud =]] installations, the [`ibexa/cloud` package](install_on_ibexa_cloud.md) performs configuration based on the `.platform.app.yaml` file.

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 [[= product_name_cloud =]] relationships and routes configuration, making it easier to configure services like databases, cache, search engines, and session storage.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The package automatically generates environment variables based on [[= product_name_cloud =]] relationships and routes configuration, making it easier to configure services like databases, cache, search engines, and session storage.
The package automatically generates environment variables based on [[= product_name_cloud =]] relationship and route configuration, making it easier to configure such services as databases, cache, search engines, and session storage.

Is it "configuration of relationships and routes" or "relationships and configurations of routes"?


### Ibexa Cloud

- Added documentation describing [how to use the new `ibexa/cloud` package](install_on_ibexa_cloud.md) and the [environment variables it provides]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Added documentation describing [how to use the new `ibexa/cloud` package](install_on_ibexa_cloud.md) and the [environment variables it provides]
- Added documentation describing [how to use the new `ibexa/cloud` package](install_on_ibexa_cloud.md) and the [environment variables it provides](environment_variables.md)

### Configuration

- Updated [DFS](clustering.md#configuring-the-dfs-io-handler) and [Solr](install_solr.md#configure-the-bundle) configuration examples to use environment variables directly with [Environment Variable Processors]([[= symfony_doc =]]/configuration/env_var_processors.html) syntax instead of intermediate parameters.
This promotes skipping rebuilding the Symfony container when environment variable values change.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This promotes skipping rebuilding the Symfony container when environment variable values change.
This helps prevent rebuilding the Symfony container when environment variable values change.

or... "This promotes skipping the rebuild of ..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs DOC review Wait with merge PRs that shouldn't be merged instantly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants