Conversation
df66a49 to
f4bdd53
Compare
|
|
||
| - `database` - main application database | ||
| - `dfs_database` - DFS database (required name for DFS functionality) | ||
| - `rediscache` - Redis for cache |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| !!! 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). |
There was a problem hiding this comment.
Should we migrate naming to "Upsun"?
| dsn: '%solr_dsn%' | ||
| core: '%solr_main_core%' | ||
| dsn: '%env(string:SOLR_DSN)%' | ||
| core: '%env(string:SOLR_MAIN_CORE)%' |
There was a problem hiding this comment.
I think *_CORE are not exposed, it's rather *_HOST now, something to be verified
If it's not supported, let's not mention it.
Yes, we are supporting it and I think @micszo tested it already |
|
Memcached mentions removed in b286cd9 |
|
| |[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| |
There was a problem hiding this comment.
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| |
There was a problem hiding this comment.
| |[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. |
There was a problem hiding this comment.
| [[= 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`. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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). |
There was a problem hiding this comment.
| 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). |
There was a problem hiding this comment.
| 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. |
There was a problem hiding this comment.
| 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] |
There was a problem hiding this comment.
| - 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. |
There was a problem hiding this comment.
| 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 ..."



Documentation for https://github.com/ibexa/cloud , including ibexa/cloud#2 and ibexa/recipes-dev#222