diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md index 15b5182422..1f94922e02 100644 --- a/docs/administration/project_organization/bundles.md +++ b/docs/administration/project_organization/bundles.md @@ -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| diff --git a/docs/getting_started/install_ibexa_dxp.md b/docs/getting_started/install_ibexa_dxp.md index 838c7ac540..8c265d0dc9 100644 --- a/docs/getting_started/install_ibexa_dxp.md +++ b/docs/getting_started/install_ibexa_dxp.md @@ -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 diff --git a/docs/getting_started/requirements.md b/docs/getting_started/requirements.md index 50d41fe640..2d59df0e84 100644 --- a/docs/getting_started/requirements.md +++ b/docs/getting_started/requirements.md @@ -410,16 +410,16 @@ 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 @@ -427,7 +427,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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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. diff --git a/docs/getting_started/troubleshooting.md b/docs/getting_started/troubleshooting.md index 53a4cf8dde..d91dcfc433 100644 --- a/docs/getting_started/troubleshooting.md +++ b/docs/getting_started/troubleshooting.md @@ -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` diff --git a/docs/ibexa_cloud/ddev_and_ibexa_cloud.md b/docs/ibexa_cloud/ddev_and_ibexa_cloud.md index a6d2000a3c..37e80c4ffc 100644 --- a/docs/ibexa_cloud/ddev_and_ibexa_cloud.md +++ b/docs/ibexa_cloud/ddev_and_ibexa_cloud.md @@ -7,7 +7,7 @@ month_change: false Two ways are available to run an [[= product_name_cloud =]] project locally with DDEV: -- [by using the `ddev-platformsh` and `ddev-ibexa-cloud` add-ons](#with-ibexa-cloud-add-ons) +- [by using the `ddev-upsun` and `ddev-ibexa-cloud` add-ons](#with-ibexa-cloud-add-ons) - [like other existing project, without these add-ons](#without-ibexa-cloud-add-ons). !!! note @@ -16,17 +16,17 @@ Two ways are available to run an [[= product_name_cloud =]] project locally with ## With Ibexa Cloud add-ons -To configure [`ddev/ddev-platformsh` add-on](https://github.com/ddev/ddev-platformsh) and [`ddev/ddev-ibexa-cloud` add-on](https://github.com/ddev/ddev-ibexa-cloud), you need a [Platform.sh API Token](https://docs.platform.sh/administration/cli/api-tokens.html). +To configure [`ddev/ddev-upsun` add-on](https://github.com/ddev/ddev-upsun) and [`ddev/ddev-ibexa-cloud` add-on](https://github.com/ddev/ddev-ibexa-cloud), you need a [Upsun API Token](https://fixed.docs.upsun.com/administration/cli/api-tokens.html). -The `ddev/ddev-platformsh` add-on configures the document root, the PHP version, the database, and the cache pool according to the [[= product_name_cloud =]] configuration. +The `ddev/ddev-upsun` add-on configures the document root, the PHP version, the database, and the cache pool according to the [[= product_name_cloud =]] configuration. About the search engine, the add-on can configure Elasticsearch but can't configure Solr. If you use Solr on [[= product_name_cloud =]] and want to add it to your DDEV stack, see [Clustering with DDEV and `ibexa/ddev-solr` add-on](clustering_with_ddev.md#solr). The `ddev/ddev-ibexa-cloud` add-on integrates the `ibexa_cloud` command inside the container, and eases the pull of cloud contents into the local installation. -`env:COMPOSER_AUTH` from Platform.sh can't be used, because JSON commas are incorrectly interpreted by `--web-environment-add`, which sees them as multiple variable separators. -But the variable must exist for Platform.sh `hooks` scripts to work. +`env:COMPOSER_AUTH` from Upsun can't be used, because JSON commas are incorrectly interpreted by `--web-environment-add`, which sees them as multiple variable separators. +But the variable must exist for Upsun `hooks` scripts to work. To use an `auth.json` file for this purpose, see [Using `auth.json`](install_with_ddev.md#using-authjson). The following sequence of commands: @@ -34,17 +34,17 @@ The following sequence of commands: 1. Downloads the [[= product_name_cloud =]] project from the default environment "production" into a new directory (for example `my-ddev-project`), using the [`ibexa_cloud` command](https://cli.ibexa.co/). (Replace `` with the hash of your own project. -See [`ibexa_cloud help get`](https://docs.platform.sh/administration/cli.html#3-use) for options like selecting another environment). +See [`ibexa_cloud help get`](https://fixed.docs.upsun.com/administration/cli.html#3-use) for options like selecting another environment). 1. Configures a new DDEV project. 1. Configures the `ddev/ddev-ibexa-cloud` add-on with ``, environment name (for example, `production`), and application name (for example, `app` from `name: app` line in `.platform.app.yaml` file). -1. Configures `ibexa_cloud` command token. See [Create an API token](https://docs.platform.sh/administration/cli/api-tokens.html#2-create-an-api-token) for more information. +1. Configures `ibexa_cloud` command token. See [Create an API token](https://fixed.docs.upsun.com/administration/cli/api-tokens.html#2-create-an-api-token) for more information. 1. Ignores `.ddev/` directory from Git. (Some DDEV config could be committed like in [this documentation](https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#extending-configyaml-with-custom-configyaml-files).) 1. Sets Composer authentication by using an already existing `auth.json` file. -1. Installs the `ddev/ddev-platformsh` add-on which prompts for the Platform.sh API token, project ID and environment name. +1. Installs the `ddev/ddev-upsun` add-on which prompts for the Upsun API token, project ID and environment name. 1. Changes `maxmemory-policy` from default `allkeys-lfu` to a [value accepted by the `RedisTagAwareAdapter`](https://github.com/symfony/cache/blob/5.4/Adapter/RedisTagAwareAdapter.php#L95). - (Check `.ddev/config.platformsh.yaml` and adapt if needed. For example, you may have to comment out New Relic.) + (Check `.ddev/config.upsun.yaml` and adapt if needed. For example, you may have to comment out New Relic.) 1. Installs the `ddev/ddev-ibexa-cloud` add-on. 1. Starts the project. 1. Gets the content from [[= product_name_cloud =]], both database and binary files by using `ddev pull ibexa-cloud` feature from the add-on. @@ -58,7 +58,7 @@ ddev config --web-environment-add IBEXA_PROJECT=,IBEXA_ENVIRONMENT=p ddev config --web-environment-add IBEXA_CLI_TOKEN= echo '.ddev/' >> .gitignore mkdir -p .ddev/homeadditions/.composer && cp /auth.json .ddev/homeadditions/.composer -ddev add-on get ddev/ddev-platformsh +ddev add-on get ddev/ddev-upsun sed -i 's/maxmemory-policy allkeys-lfu/maxmemory-policy volatile-lfu/' .ddev/redis/redis.conf ddev add-on get ddev/ddev-ibexa-cloud ddev start @@ -69,24 +69,24 @@ ddev launch !!! note - The Platform.sh API token is set at user profile level, therefore it's stored globally under current user root as `PLATFORMSH_CLI_TOKEN` in `~/.ddev/global_config.yaml`. + The Upsun API token is set at user profile level, therefore it's stored globally under current user root as `PLATFORMSH_CLI_TOKEN` in `~/.ddev/global_config.yaml`. ## Without Ibexa Cloud add-ons -The following example adapts the [manual method to run an already existing project](install_with_ddev.md#run-an-already-existing-project) to the Platform.sh case: +The following example adapts the [manual method to run an already existing project](install_with_ddev.md#run-an-already-existing-project) to the Upsun case: The following sequence of commands: -1. Downloads the [[= product_name_cloud =]] Platform.sh project from the default environment "production" into a new directory, using the [[[= product_name_cloud =]] CLI](https://cli.ibexa.co/). -(Replace `` with the hash of your own project. See [`ibexa_cloud help get`](https://docs.platform.sh/administration/cli.html#3-use) for options like selecting another environment). +1. Downloads the [[= product_name_cloud =]] Upsun project from the default environment "production" into a new directory, using the [[[= product_name_cloud =]] CLI](https://cli.ibexa.co/). +(Replace `` with the hash of your own project. See [`ibexa_cloud help get`](https://fixed.docs.upsun.com/administration/cli.html#3-use) for options like selecting another environment). 1. Configures a new DDEV project. 1. Ignores `.ddev/` directory from Git. (Some DDEV config could be committed like in [this documentation](https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#extending-configyaml-with-custom-configyaml-files).) 1. Starts the DDEV project. 1. Sets Composer authentication. -1. [Gets the database content from Platform.sh](https://docs.platform.sh/add-services/mysql.html#exporting-data). +1. [Gets the database content from Upsun](https://fixed.docs.upsun.com/add-services/mysql.html#exporting-data). 1. [Imports this database content into DDEV project's database](https://ddev.readthedocs.io/en/latest/users/usage/database-management/#database-imports). -1. [Downloads the Platform.sh public/var locally](https://docs.platform.sh/development/file-transfer.html#transfer-a-file-from-a-mount) to have the content binary files. +1. [Downloads the Upsun public/var locally](https://fixed.docs.upsun.com/development/file-transfer.html#transfer-a-file-from-a-mount) to have the content binary files. 1. Install the dependencies and run post-install scripts. 1. Displays information about the project services. 1. Opens the DDEV project in a browser. @@ -105,6 +105,6 @@ ddev describe ddev launch ``` -From there, services can be added to get closer to [[= product_name_cloud =]] Platform.sh architecture. +From there, services can be added to get closer to [[= product_name_cloud =]] architecture. `.platform/services.yaml` indicates the services used. For more information, see [Clustering with DDEV](clustering_with_ddev.md). diff --git a/docs/ibexa_cloud/ibexa_cloud.md b/docs/ibexa_cloud/ibexa_cloud.md index 2635127a5d..0db9ef09ab 100644 --- a/docs/ibexa_cloud/ibexa_cloud.md +++ b/docs/ibexa_cloud/ibexa_cloud.md @@ -6,7 +6,7 @@ month_change: false # [[= product_name_cloud =]] -[[= product_name_cloud =]] is a cloud hosting platform that enables you to host your application in the cloud by using the Platform.sh service. +[[= product_name_cloud =]] is a cloud hosting platform that enables you to host your application in the cloud by using the Upsun service. [[= cards([ "ibexa_cloud/ibexa_cloud_guide", diff --git a/docs/ibexa_cloud/ibexa_cloud_guide.md b/docs/ibexa_cloud/ibexa_cloud_guide.md index dac8cfb8f6..b85896b1af 100644 --- a/docs/ibexa_cloud/ibexa_cloud_guide.md +++ b/docs/ibexa_cloud/ibexa_cloud_guide.md @@ -8,7 +8,7 @@ month_change: false ## What is [[= product_name_cloud =]] -[[= product_name_cloud =]] is a cloud hosting platform that enables you to host your application in the cloud by using the [Platform.sh](https://platform.sh/) service. +[[= product_name_cloud =]] is a cloud hosting platform that enables you to host your application in the cloud by using the [Upsun](https://upsun.com/) service. It also establishes the framework for the potential growth and improves project delivery. As a diverse Platform as a Service (PaaS), it's designed to allow you to focus on the crucial things. @@ -51,7 +51,7 @@ All you have to do is access it and you can start deploying resources and develo ### Performance management -Make your applications more effective, scalable, and effective by using the [Observability Suite](https://platform.sh/features/observability-suite/). +Make your applications more effective, scalable, and effective by using the [Observability Suite](https://docs.upsun.com/increase-observability.html). This package gives you the ability to test, profile, and monitor your application before putting it into production. Observability Suite comes with each [[= product_name_cloud =]] subscription. @@ -89,9 +89,9 @@ It's a Git-native development - compatible with Git Flow. [[= product_name_cloud =]] deployment integrates naturally at the end of your existing production chain, including staging, and work in progress branch preview. You can also integrate with, for example, Bitbucket, GitHub, GitLab. You can instantly clone every branch of both your code and infrastructure configuration. -Platform.sh (and [[= product_name_cloud =]], by extension) uses the [Infrastructure as Code approach](https://docs.platform.sh/learn/overview.html#infrastructure-as-code). +Upsun (and [[= product_name_cloud =]], by extension) uses the [Infrastructure as Code approach](https://fixed.docs.upsun.com/learn/overview.html#infrastructure-as-code). It means that the infrastructure is described in the code and that is what allows you to clone both code and infrastructure configuration at the same time. -If you want to work with services such as [MySQL](https://docs.platform.sh/add-services/mysql.html) or [Elasticsearch](https://docs.platform.sh/add-services/elasticsearch.html), you can add them with a line of code. +If you want to work with services such as [MySQL](https://fixed.docs.upsun.com/add-services/mysql.html) or [Elasticsearch](https://fixed.docs.upsun.com/add-services/elasticsearch.html), you can add them with a line of code. What's more, you can run in your chosen cloud, like Microsoft Azure, Orange, or Google Cloud Platform. ### Great customer experience @@ -121,12 +121,12 @@ Team members can also see and provide input on the new feature's actual appearan ### Integrated customer support -Support integration is a part of the combined Platform.sh and [[= product_name_base =]] service. +Support integration is a part of the combined Upsun and [[= product_name_base =]] service. In case of an issue, you only have to submit one ticket, no matter whether it has to do with [[= product_name =]] or the cloud infrastructure. When you submit a ticket with [[= product_name_cloud =]], the support team looks into the issue and assigns it to the appropriate expert. ### Lower cost With PaaS solution there is no need to purchase and maintain hardware or software infrastructure. This reduces the total cost of ownership and operational expenses. -According to [Forrester Total Economic Impact report](https://platform.sh/blog/platform-sh-drives-meaningful-cost-savings/) from March 2022, a company that uses Platform.sh for three years achieves an investment return of 219%. -According to this in-depth analysis, Platform.sh reduces operating expenses for developers and IT by $1 million over the course of three years, and in as little as seven months, break-even point can be reached. +According to [Forrester Total Economic Impact report](https://devcenter.upsun.com/posts/platform-sh-drives-meaningful-cost-savings/) from March 2022, a company that uses Upsun for three years achieves an investment return of 219%. +According to this in-depth analysis, Upsun reduces operating expenses for developers and IT by $1 million over the course of three years, and in as little as seven months, break-even point can be reached. diff --git a/docs/ibexa_cloud/install_on_ibexa_cloud.md b/docs/ibexa_cloud/install_on_ibexa_cloud.md index 044f80ce04..93acca46e1 100644 --- a/docs/ibexa_cloud/install_on_ibexa_cloud.md +++ b/docs/ibexa_cloud/install_on_ibexa_cloud.md @@ -5,7 +5,7 @@ month_change: false # Install on Ibexa Cloud -[[= product_name_cloud =]] enables you to host your application in the cloud by using the [Platform.sh](https://platform.sh/) service. +[[= product_name_cloud =]] enables you to host your application in the cloud by using the [Upsun](https://upsun.com/) service. ## 1. Prepare configuration files @@ -23,7 +23,7 @@ You can adapt the configuration in the following places: - `.platform/services.yml` - additional services such as search engines or cache - `.platform/routes.yml` - routes to additional services, for example Fastly -For details about available configuration settings, refer to [Platform.sh documentation](https://docs.platform.sh/create-apps.html). +For details about available configuration settings, refer to [Upsun documentation](https://fixed.docs.upsun.com/create-apps.html). ### Disk space @@ -45,7 +45,7 @@ Configuration under `hooks` defines the process of building and deploying your p `.platform/services.yaml` contains preconfigured setting blocks that you can uncomment to enable services such as Solr or Elasticsearch, or persistent Redis session storage. -For information about available services, see [Platform.sh documentation](https://docs.platform.sh/add-services.html#available-services). +For information about available services, see [Upsun documentation](https://fixed.docs.upsun.com/add-services.html#available-services). If you enable any of the services, you must uncomment the relevant relationship under the `relationship` key in `.platform.app.yaml` as well. @@ -57,18 +57,18 @@ Create a project and select its region. !!! caution - Don't use https://console.platform.sh/ which doesn't list [[= product_name_cloud =]] projects. + Don't use https://console.upsun.com/ (or former https://console.platform.sh/) which don't list [[= product_name_cloud =]] projects. Use https://console.ibexa.cloud to manage your [[= product_name_cloud =]] projects. ## 3. Prepare for hosting After the project is created, the website walks you through preparing your project for hosting. -This includes adding an SSH key, and adding Platform.sh as a git remote. +This includes adding an SSH key, and adding Upsun as a git remote. -Add your Composer authentication token to the project before pushing it to Platform.sh. +Add your Composer authentication token to the project before pushing it to Upsun. You can set this token as an environment variable. -When you do, make sure the **Visible during runtime** box in Platform.sh configuration is unchecked. +When you do, make sure the **Visible during runtime** box in [[= product_name_cloud =]] configuration is unchecked. This ensures that the token isn't exposed. ### Composer authentication using the web console @@ -87,10 +87,10 @@ ibexa_cloud variable:create --level project --name env:COMPOSER_AUTH \ ## 4. Push the project -When you're done with configuration, push your project to the Platform.sh remote: +When you're done with configuration, push your project to the Upsun remote: ``` bash -git push -u main +git push -u main ``` You can also use the [[[= product_name_cloud =]] CLI](https://cli.ibexa.cloud/) to push your code. @@ -101,15 +101,15 @@ ibexa_cloud push main !!! note - `main` is the Platform.sh name for the production branch. + `main` is the Upsun name for the production branch. !!! caution - Don't use Platform.sh CLI (`platform`), instead, use the [[[= product_name_cloud =]] CLI (`ibexa_cloud`)](https://cli.ibexa.cloud/). + Don't use Upsun CLI (`upsun`), instead, use the [[[= product_name_cloud =]] CLI (`ibexa_cloud`)](https://cli.ibexa.cloud/). To install [[= product_name_cloud =]] CLI, follow https://cli.ibexa.cloud/ "Installation instructions". - [[= product_name_cloud =]] CLI and Platform.sh CLI share the same commands and the [same documentation](https://docs.platform.sh/administration/cli.html#3-use), but you have to replace `platform` with `ibexa_cloud`. + [[= product_name_cloud =]] CLI and Upsun CLI share the same commands and the [same documentation](https://fixed.docs.upsun.com/administration/cli.html#3-use), but you have to replace `upsun` with `ibexa_cloud`. - If you have previously set up an alias to use Platform.sh CLI with [[= product_name_cloud =]], it's outdated. + If you have previously set up an alias to use Upsun CLI with [[= product_name_cloud =]], it's outdated. Remove the alias and install [[= product_name_cloud =]] CLI instead. diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md index 4427567fe7..f0d78ca02d 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md @@ -364,7 +364,7 @@ This section describes to how to debug problems related to HTTP cache. the HTTP cache sends to the client (web browser). It means you must be able to send requests to your origin (web server) that don't go through Varnish or Fastly. If you run Nginx and Varnish on premise, you should know what host and port number both Varnish and Nginx runs on. - If you perform tests on Fastly enabled environment on [[= product_name_cloud =]] provided by Platform.sh, you need to use the Platform.sh + If you perform tests on Fastly enabled environment on [[= product_name_cloud =]] provided by Upsun, you need to use the Upsun dashboard to obtain the endpoint for Nginx. The following example shows how to debug and check why Fastly doesn't cache the front page properly. @@ -380,17 +380,17 @@ HTTP/2 200 x-cache: MISS ``` -### Nginx endpoint on Platform.sh +### Nginx endpoint on [[= product_name_cloud =]] #### Finding Nginx endpoint for environments located on the grid To find the Nginx point, first, you need to know in which region your project is located. -To do that, go to the Platform.sh dashboard. +To do that, go to the [[= product_name_cloud =]] dashboard. To find a valid route, click an element in the **URLs** drop-down for the specified environment and select the route. A route may look like this: `https://www.staging.foobar.com.us-2.platformsh.site/` -In this case the region is `us-2` and you can find the public IP list on [Platform.sh documentation page](https://docs.platform.sh/development/regions.html#public-ip-addresses). +In this case the region is `us-2` and you can find the public IP list on [Upsun documentation page](https://fixed.docs.upsun.com/development/regions.html#public-ip-addresses). Typically, you can add a `gw` to the hostname and use nslookup to find it. ```bash @@ -400,7 +400,7 @@ Typically, you can add a `gw` to the hostname and use nslookup to find it. Address: 1.2.3.4 ``` -You can also use the [[[= product_name_cloud =]] CLI](https://cli.ibexa.co/) (which has the same command as the Platform.sh CLI) to find [the endpoint](https://docs.platform.sh/domains/steps/dns.html): +You can also use the [[[= product_name_cloud =]] CLI](https://cli.ibexa.co/) (which has the same command as the Upsun CLI) to find [the endpoint](https://fixed.docs.upsun.com/domains/steps/dns.html): ```bash ibexa_cloud environment:info edge_hostname @@ -408,8 +408,8 @@ You can also use the [[[= product_name_cloud =]] CLI](https://cli.ibexa.co/) (wh #### Finding Nginx endpoint on dedicated cloud -If you have a dedicated 3-node cluster on Platform.sh, the procedure for getting the endpoint to environments that are located on that cluster (`production` and sometimes also `staging`) is slightly different. -In the **URLs** drop-down in the Platform.sh dashboard, find the route that has the format `somecontent.[clusterid].ent.platform.sh/`, for example, `myenvironment.abcdfg2323.ent.platform.sh/` +If you have a dedicated 3-node cluster on Upsun, the procedure for getting the endpoint to environments that are located on that cluster (`production` and sometimes also `staging`) is slightly different. +In the **URLs** drop-down in the [[= product_name_cloud =]] dashboard, find the route that has the format `somecontent.[clusterid].ent.platform.sh/`, for example, `myenvironment.abcdfg2323.ent.platform.sh/` The endpoint in case has the format `c.[clusterid].ent.platform.sh`, for example, `c.asddfs2323.ent.platform.sh/`. Next, use nslookup to find the IP: @@ -440,7 +440,7 @@ Some notes about each of these parameters: - We tell curl not to do a DNS lookup for `www.staging.foobar.com.us-2.platformsh.site`. We do that because in our case that resolves to the Fastly endpoint, not our origin (nginx) - We specify `443` because we are using `https` - - We provide the IP of the nginx endpoint at platform.sh (`1.2.3.4` in this example) + - We provide the IP of the nginx endpoint at Upsun (`1.2.3.4` in this example) - `--header "Surrogate-Capability: abc=ESI/1.0"`, strictly speaking not needed when fetching the user-context-hash, but this tells [[= product_name =]] that client understands ESI tags. It's good practice to always include this header when imitating the HTTP Cache. - `--header "accept: application/vnd.fos.user-context-hash"` tells [[= product_name =]] that the client wants to receive the user-context-hash diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md b/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md index 09e3153bf4..a3431bef21 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/fastly.md @@ -17,7 +17,7 @@ The information provided here is only applicable if you want to change the defau !!! note "Disable Varnish when you use Fastly" Varnish is automatically provisioned on [[= product_name_cloud =]]. Varnish needs to be disabled on all environments that use - Fastly. See [documentation on how to do that](https://docs.platform.sh/guides/ibexa/fastly.html). + Fastly. See [documentation on how to do that](https://fixed.docs.upsun.com/guides/ibexa/fastly.html). ## Prepare for using Fastly locally diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md index 488a1b2409..220c40afac 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md @@ -84,7 +84,7 @@ framework: !!! caution "Careful when trusting dynamic IP that uses `REMOTE_ADDR` value or similar" - On Platform.sh, Varnish doesn't have a static IP, like with [AWS LB]([[= symfony_doc =]]/deployment/proxies.html#but-what-if-the-ip-of-my-reverse-proxy-changes-constantly). + On Upsun, Varnish doesn't have a static IP, like with [AWS LB]([[= symfony_doc =]]/deployment/proxies.html#but-what-if-the-ip-of-my-reverse-proxy-changes-constantly). For this reason, the `TRUSTED_PROXIES` env variable supports being set to value `REMOTE_ADDR`, which is equal to: ```php @@ -100,8 +100,8 @@ When using Fastly, you need to set `trusted_proxies` according to the [IP ranges !!! tip - You don't have to set `trusted_proxies` when using Fastly on Platform.sh. - The Platform.sh router automatically changes the source IP of requests coming from Fastly, replacing the source IP with the actual client IP and removing any `X-FORWARD-...` header in the request before it reaches [[= product_name =]]. + You don't have to set `trusted_proxies` when using Fastly on Upsun. + The Upsun router automatically changes the source IP of requests coming from Fastly, replacing the source IP with the actual client IP and removing any `X-FORWARD-...` header in the request before it reaches [[= product_name =]]. For more information about setting these variables, see [Configuration examples](#configuration-examples). @@ -233,10 +233,10 @@ FASTLY_SERVICE_ID="ID" FASTLY_KEY="token" ``` -#### Configure Fastly on Platform.sh +#### Configure Fastly on [[= product_name_cloud =]] -If you use Platform.sh, it's recommended to configure all environment variables through [Platform.sh variables](https://docs.platform.sh/guides/ibexa/fastly.html). -In [[= product_name =]], Varnish is enabled by default. To use Fastly, first you must [disable Varnish](https://docs.platform.sh/guides/ibexa/fastly.html#remove-varnish-configuration). +If you use Upsun, it's recommended to configure all environment variables through [Upsun variables](https://fixed.docs.upsun.com/guides/ibexa/fastly.html). +In [[= product_name =]], Varnish is enabled by default. To use Fastly, first you must [disable Varnish](https://fixed.docs.upsun.com/guides/ibexa/fastly.html#remove-varnish-configuration). #### Get Fastly service ID and API token @@ -272,9 +272,9 @@ fastcgi_param HTTPCACHE_PURGE_TYPE varnish; fastcgi_param HTTPCACHE_PURGE_SERVER "http://varnish:80"; ``` -Example for Platform.sh: +Example for Upsun: -You can configure environment variables through [Platform.sh variables](https://docs.platform.sh/guides/ibexa/fastly.html). +You can configure environment variables through [Upsun variables](https://fixed.docs.upsun.com/guides/ibexa/fastly.html). !!! tip diff --git a/docs/infrastructure_and_maintenance/cache/persistence_cache.md b/docs/infrastructure_and_maintenance/cache/persistence_cache.md index 55cc0a1dcc..b11e0bb15c 100644 --- a/docs/infrastructure_and_maintenance/cache/persistence_cache.md +++ b/docs/infrastructure_and_maintenance/cache/persistence_cache.md @@ -156,7 +156,7 @@ Out of the box in `config/packages/cache_pool/cache.redis.yaml` you can find a d !!! 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 =]]: This is automatically configured in `vendor/ibexa/core/src/bundle/Core/DependencyInjection/IbexaCoreExtension.php` if you have enabled Redis as `rediscache` Upsun service. For anything else, you can enable it with environment variables. For instance, if you set the following environment variables `export CACHE_POOL="cache.redis" CACHE_DSN="secret@example.com:1234/13"`, it results in config like this: @@ -203,12 +203,12 @@ Several cloud providers have managed services that are easier to set up, handle - [Azure Redis Cache](https://azure.microsoft.com/en-us/products/cache/) - [Google Cloud Memorystore](https://cloud.google.com/memorystore) -###### [[= product_name_cloud =]] / Platform.sh usage +###### [[= product_name_cloud =]] usage !!! note "[[= product_name_cloud =]]" - If you use Platform.sh Enterprise you can benefit from the Redis Sentinel across three nodes for great fault tolerance. - Platform.sh Professional and lower versions offer Redis in single instance mode only. + If you use Upsun Enterprise you can benefit from the Redis Sentinel across three nodes for great fault tolerance. + Upsun Professional and lower versions offer Redis in single instance mode only. ### Memcached @@ -234,7 +234,7 @@ Out of the box in `config/packages/cache_pool/cache.memcached.yaml` you can find !!! 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 Memcached as `cache` Platform.sh service. + For [[= product_name_cloud =]]: This is automatically configured in `vendor/ibexa/core/src/bundle/Core/DependencyInjection/IbexaCoreExtension.php` if you have enabled Memcached as `cache` Upsun service. For anything else, you can enable it with environment variables detected automatically by `vendor/ibexa/core/src/bundle/Core/DependencyInjection/IbexaCoreExtension.php`. For instance, if you set the following environment variables `export CACHE_POOL="cache.memcached" CACHE_DSN="user:pass@localhost?weight=33"`, it results in config like this: diff --git a/docs/infrastructure_and_maintenance/clustering/clustering.md b/docs/infrastructure_and_maintenance/clustering/clustering.md index f7345353b5..cf720ebf20 100644 --- a/docs/infrastructure_and_maintenance/clustering/clustering.md +++ b/docs/infrastructure_and_maintenance/clustering/clustering.md @@ -51,7 +51,7 @@ To avoid concurrent access to session data from front-end nodes, if possible you Session locking is available with `php-memcached`, and with `php-redis` (v4.2.0 and higher). -On [[= product_name_cloud =]] (and Platform.sh) Redis is preferred and supported. +On [[= product_name_cloud =]] (and Upsun) Redis is preferred and supported. ### Shared binary files @@ -137,7 +137,7 @@ For production, it's recommended to create the DFS table in its own database, ma ``` !!! note - On [[= product_name_cloud =]] (and Platform.sh) a separate DFS database is supported for MySQL only. + On [[= product_name_cloud =]] a separate DFS database is supported for MySQL only. This example uses Doctrine connection named `dfs`: diff --git a/docs/infrastructure_and_maintenance/security/security_checklist.md b/docs/infrastructure_and_maintenance/security/security_checklist.md index b5d03c842a..63c5fdd4be 100644 --- a/docs/infrastructure_and_maintenance/security/security_checklist.md +++ b/docs/infrastructure_and_maintenance/security/security_checklist.md @@ -172,7 +172,7 @@ This applies also to other secrets that may be in use, like the Varnish invalida !!! note - On [[= product_name_cloud =]], if `APP_SECRET` isn't set, the system sets it to [`PLATFORM_PROJECT_ENTROPY`](https://docs.platform.sh/guides/symfony/environment-variables.html#symfony-environment-variables) + On [[= product_name_cloud =]], if `APP_SECRET` isn't set, the system sets it to [`PLATFORM_PROJECT_ENTROPY`](https://fixed.docs.upsun.com/guides/symfony/environment-variables.html#symfony-environment-variables) ### Symfony production mode @@ -251,7 +251,7 @@ Removing them means that attackers can't attempt to force other users to use wea As of December 2024, TLS 1.3 is [supported by ca. 97% of global internet users](https://caniuse.com/tls1-3). If you need to support Internet Explorer or old versions of other browsers, you can disable TLS 1.1 and older, leaving 1.2 and 1.3 enabled. -When using [[= product_name_cloud =]], you can [set the minimum TLS version in `.platform/routes.yaml`](https://docs.platform.sh/define-routes/https.html#enforce-tls-13). +When using [[= product_name_cloud =]], you can [set the minimum TLS version in `.platform/routes.yaml`](https://fixed.docs.upsun.com/define-routes/https.html#enforce-tls-13). ### Enable HTTP Strict Transport Security (HSTS) @@ -260,7 +260,7 @@ HSTS forces clients to always communicate with your site over HTTPS. Read the requirements and instructions at [hstspreload.org](https://hstspreload.org/) before you enable HSTS. Make sure to also include subdomains by means of the `includeSubDomains` setting. -When using [[= product_name_cloud =]], you can [configure HSTS in `.platform/routes.yaml`](https://docs.platform.sh/define-routes/https.html#enable-http-strict-transport-security-hsts). +When using [[= product_name_cloud =]], you can [configure HSTS in `.platform/routes.yaml`](https://fixed.docs.upsun.com/define-routes/https.html#enable-http-strict-transport-security-hsts). Beware if you are using a Varnish proxy: Your version of Varnish may not support HTTPS connections with your web server. diff --git a/docs/infrastructure_and_maintenance/sessions.md b/docs/infrastructure_and_maintenance/sessions.md index 9aae0b923d..488538c417 100644 --- a/docs/infrastructure_and_maintenance/sessions.md +++ b/docs/infrastructure_and_maintenance/sessions.md @@ -114,7 +114,7 @@ Alternatively if you have needs to configure Redis servers dynamically: !!! note "[[= product_name_cloud =]]" - For [[= product_name_cloud =]] (and Platform.sh), this is already configured in `config/env/platformsh.php` based on `.platform.yaml` config. + For [[= product_name_cloud =]], this is already configured based on `.platform.app.yaml` config. If you're on `php-redis` v4.2.0 and higher, you can optionally tweak [`php-redis` settings](https://github.com/phpredis/phpredis#session-locking) for session locking. diff --git a/docs/search/search_engines/solr_search_engine/install_solr.md b/docs/search/search_engines/solr_search_engine/install_solr.md index 7fd54664a6..c9c540c58d 100644 --- a/docs/search/search_engines/solr_search_engine/install_solr.md +++ b/docs/search/search_engines/solr_search_engine/install_solr.md @@ -147,7 +147,7 @@ Add this `spellcheck` component to the `/select` request handler: ### Generate Solr configuration automatically The command line tool `bin/generate-solr-config.sh` generates Solr configuration automatically. -It can be used for deploying to [[= product_name_cloud =]] (Platform.sh) and on-premise installs. +It can be used for deploying to [[= product_name_cloud =]] (Upsun) and on-premise installs. Execute the script from the [[= product_name =]] root directory for further information: