Conversation
mnocon
force-pushed
the
ibea-cloud
branch
2 times, most recently
from
df66a49 to
f4bdd53
Compare
|
|
||
| - `database` - main application database | ||
| - `dfs_database` - DFS database (required name for DFS functionality) | ||
| - `rediscache` - Redis for cache |
There was a problem hiding this comment.
I wonder if the strict naming requirement makes sense now - Redis, Elasticsearch, Solr and databases don't have to be named in any specific way. The only required ones are dfs_database and redissession.
Developers can have multirepo setup with many services, and environmental variables are exposed accordingly. So maybe we shouldn't enforce the setup with word "use" - wdyt?
| !!! 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 |
|
2 participants
Documentation for https://github.com/ibexa/cloud , including ibexa/cloud#2 and ibexa/recipes-dev#222