Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/administration/project_organization/bundles.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ To remove a bundle (either one you created yourself, or an out-of-the-box one th
|ibexa/calendar|Calendar tab with a calendar widget|
|ibexa/connector-dam|Connector for DAM (Digital Asset Management) systems|
|ibexa/elasticsearch|Integration with Elasticsearch search engine|
|ibexa/fastly|Fastly support for `http-cache`, for use on Platform.sh or standalone|
|ibexa/fastly|Fastly support for `http-cache`, for use on [[= product_name_cloud =]] or standalone|
|ibexa/icons|Icon set for the back office|
|ibexa/image-editor|[Image Editor](configure_image_editor.md)|
|ibexa/installer|Provides the `ibexa:install` command|
Expand Down
6 changes: 3 additions & 3 deletions docs/getting_started/install_ibexa_dxp.md
Original file line number Diff line number Diff line change
Expand Up @@ -171,15 +171,15 @@ To use Composer to instantly create a project in the current folder with all the
composer create-project ibexa/experience-skeleton:[[= latest_tag_4_6 =]] .
```

!!! note "Platform.sh"
!!! note "[[= product_name_cloud =]]"

If you're deploying your installation on [Platform.sh](https://docs.platform.sh/guides/ibexa/deploy.html), run the following command:
If you're deploying your installation on [Upsun](https://fixed.docs.upsun.com/guides/ibexa/deploy.html), run the following command:

``` bash
composer ibexa:setup --platformsh
```

This command provides the necessary configuration for using Platform.sh.
This command provides the necessary configuration for using [[= product_name_cloud =]].

#### Add project to version control

Expand Down
48 changes: 24 additions & 24 deletions docs/getting_started/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -410,24 +410,24 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

=== "[[= product_name =]] v5.0"

### Cloud hosting with [[= product_name_cloud =]] and Platform.sh
### Cloud hosting with [[= product_name_cloud =]] and Upsun

In general, [[= product_name_cloud =]] supports all features and services of [Platform.sh](https://platform.sh/marketplace/ibexa/) that are compatible and supported by the [[= product_name =]] version you use.
In general, [[= product_name_cloud =]] supports all features and services of [Upsun](https://fixed.docs.upsun.com/add-services.html#available-services) that are compatible and supported by the [[= product_name =]] version you use.

For example:

- Platform.sh provides Redis support for versions 7.2, 7.0, and 6.2. [[= product_name =]] supports Redis version 7.2.
- Upsun provides Redis support for versions 7.2, 7.0, and 6.2. [[= product_name =]] supports Redis version 7.2.
As a result, Redis is supported on [[= product_name_cloud =]] in versions 7.2.

Features or services supported by [[= product_name =]] but not covered by Platform.sh may be possible by means of a [custom integration](#custom-integrations).
Features or services supported by [[= product_name =]] but not covered by Upsun may be possible by means of a [custom integration](#custom-integrations).

### [[= product_name_cloud =]] Setup support matrix

All [[= product_name =]] features are supported in accordance with the example above.

!!! note

As Platform.sh doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Platform.sh it's impossible to have a DFS table in a separate database.
As Upsun doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Upsun it's impossible to have a DFS table in a separate database.

### Recommended [[= product_name_cloud =]] setup

Expand All @@ -441,31 +441,31 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

Make sure to set aside time and budget for:

- Verifying your requirements and ensuring they're supported by Platform.sh
- Verifying your requirements and ensuring they're supported by Upsun
- Additional time for adaptation and configuration work, and testing by your development team
- Additional consulting/onboarding time with Platform.sh, Ibexa technical services, and/or one of the many partners with prior experience in using Platform.sh with [[= product_name =]]
- Additional consulting/onboarding time with Upsun, Ibexa technical services, and/or one of the many partners with prior experience in using Upsun with [[= product_name =]]

The cost and effort of this isn't included in [[= product_name_cloud =]] subscription and is vary depending on the project.

### Custom integrations

Features supported by [[= product_name =]], but not natively by Platform.sh, can in many cases be used by means of custom integrations with external services.
Features supported by [[= product_name =]], but not natively by Upsun, can in many cases be used by means of custom integrations with external services.

For example, you can create an integration with S3 by means of setting up your own S3 bucket and configuring the relevant parts of [[= product_name =]].
We recommend giving the development team working on the project access to the bucket to ensure work is done in a DevOps way without depending on external teams when changes are needed.

=== "[[= product_name =]] v4.6"

### Cloud hosting with [[= product_name_cloud =]] and Platform.sh
### Cloud hosting with [[= product_name_cloud =]] and Upsun

In general, [[= product_name_cloud =]] supports all features and services of [Platform.sh](https://platform.sh/marketplace/ibexa/) that are compatible and supported by the [[= product_name =]] version you use.
In general, [[= product_name_cloud =]] supports all features and services of [Upsun](https://fixed.docs.upsun.com/add-services.html#available-services) that are compatible and supported by the [[= product_name =]] version you use.

For example:

- Platform.sh provides Redis support for versions 7.2, 7.0, and 6.2. [[= product_name =]] supports Redis in versions 4.0, 5.0, and 7.2.
- Upsun provides Redis support for versions 7.2, 7.0, and 6.2. [[= product_name =]] supports Redis in versions 4.0, 5.0, and 7.2.
As a result, Redis is supported on [[= product_name_cloud =]] in version 7.2.

Features or services supported by [[= product_name =]] but not covered by Platform.sh may be possible by means of a [custom integration](#custom-integrations).
Features or services supported by [[= product_name =]] but not covered by Upsun may be possible by means of a [custom integration](#custom-integrations).

### [[= product_name_cloud =]] Setup support matrix

Expand All @@ -474,7 +474,7 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

!!! note

As Platform.sh doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Platform.sh it's impossible to have a DFS table in a separate database.
As Upsun doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Upsun it's impossible to have a DFS table in a separate database.

### Recommended [[= product_name_cloud =]] setup

Expand All @@ -488,31 +488,31 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

Make sure to set aside time and budget for:

- Verifying your requirements and ensuring they're supported by Platform.sh
- Verifying your requirements and ensuring they're supported by Upsun
- Additional time for adaptation and configuration work, and testing by your development team
- Additional consulting/onboarding time with Platform.sh, Ibexa technical services, and/or one of the many partners with prior experience in using Platform.sh with [[= product_name =]]
- Additional consulting/onboarding time with Upsun, Ibexa technical services, and/or one of the many partners with prior experience in using Upsun with [[= product_name =]]

The cost and effort of this isn't included in [[= product_name_cloud =]] subscription and is vary depending on the project.

### Custom integrations

Features supported by [[= product_name =]], but not natively by Platform.sh, can in many cases be used by means of custom integrations with external services.
Features supported by [[= product_name =]], but not natively by Upsun, can in many cases be used by means of custom integrations with external services.

For example, you can create an integration with S3 by means of setting up your own S3 bucket and configuring the relevant parts of [[= product_name =]].
We recommend giving the development team working on the project access to the bucket to ensure work is done in a DevOps way without depending on external teams when changes are needed.

=== "[[= product_name =]] v3.3"

### Cloud hosting with [[= product_name_cloud =]] and Platform.sh
### Cloud hosting with [[= product_name_cloud =]] and Upsun

In general, [[= product_name_cloud =]] supports all features and services of [Platform.sh](https://platform.sh/marketplace/ibexa/) that are compatible and supported by the [[= product_name =]] version you use.
In general, [[= product_name_cloud =]] supports all features and services of [Upsun](https://fixed.docs.upsun.com/add-services.html#available-services) that are compatible and supported by the [[= product_name =]] version you use.

For example:

- Platform.sh provides Redis support for versions 3.2, 4.0 and 5.0. [[= product_name =]] supports Redis version 4.0 or higher, and recommends 5.0.
- Upsun provides Redis support for versions 3.2, 4.0 and 5.0. [[= product_name =]] supports Redis version 4.0 or higher, and recommends 5.0.
As a result, Redis is supported on [[= product_name_cloud =]] in versions 4.0 and 5.0, but 5.0 is recommended.

Features or services supported by [[= product_name =]] but not covered by Platform.sh may be possible by means of a [custom integration](#custom-integrations_1).
Features or services supported by [[= product_name =]] but not covered by Upsun may be possible by means of a [custom integration](#custom-integrations_1).

### [[= product_name_cloud =]] Setup support matrix

Expand All @@ -521,7 +521,7 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

!!! note

As Platform.sh doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Platform.sh it's impossible to have a DFS table in a separate database.
As Upsun doesn't support a configuration with multiple PostgreSQL databases, for [[= product_name_cloud =]] / Upsun it's impossible to have a DFS table in a separate database.

### Recommended [[= product_name_cloud =]] setup

Expand All @@ -535,15 +535,15 @@ For production setups it's recommended that you use Varnish/Fastly, Redis, NFS/E

Make sure to set aside time and budget for:

- Verifying your requirements and ensuring they're supported by Platform.sh
- Verifying your requirements and ensuring they're supported by Upsun
- Additional time for adaptation and configuration work, and testing by your development team
- Additional consulting/onboarding time with Platform.sh, Ibexa technical services, and/or one of the many partners with prior experience in using Platform.sh with [[= product_name =]]
- Additional consulting/onboarding time with Upsun, Ibexa technical services, and/or one of the many partners with prior experience in using Upsun with [[= product_name =]]

The cost and effort of this isn't included in [[= product_name_cloud =]] subscription and is vary depending on the project.

### Custom integrations

Features supported by [[= product_name =]], but not natively by Platform.sh, can in many cases be used by means of custom integrations with external services.
Features supported by [[= product_name =]], but not natively by Upsun, can in many cases be used by means of custom integrations with external services.

For example, you can create an integration with S3 by means of setting up your own S3 bucket and configuring the relevant parts of [[= product_name =]].
We recommend giving the development team working on the project access to the bucket to ensure work is done in a DevOps way without depending on external teams when changes are needed.
4 changes: 2 additions & 2 deletions docs/getting_started/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ In the rare case when there is no fixed version, you can revert your requirement
If you have to use the version with the bug (not recommended) you can use `composer remove roave/security-advisories`.
In such case, require it again when the bug is fixed and the package is updated: `composer require roave/security-advisories:dev-master` 

## Platform.sh HTTP access credentials with Varnish
## [[= product_name_cloud =]] HTTP access credentials with Varnish

If you're using Platform.sh with Varnish for HTTP cache and you have [HTTP access control by login/password](https://docs.platform.sh/administration/web/configure-environment.html#http-access-control) enabled, configure the following variables in your Platform.sh environment:
If you're using [[= product_name_cloud =]] with Varnish for HTTP cache and you have [HTTP access control by login/password](https://fixed.docs.upsun.com/administration/web/configure-environment.html#http-access-control) enabled, configure the following variables in your Upsun environment:

- `HTTPCACHE_USERNAME`
- `HTTPCACHE_PASSWORD`
Loading