> ## Documentation Index > Fetch the complete documentation index at: https://developer.upsun.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy Bedrock-based WordPress on Upsun Cloud > Complete the last required steps to successfully deploy Bedrock-based WordPress on Upsun Cloud using Bedrock. > [!NOTE] > > Before you start, check out the [Upsun Cloud demo app](https://console.upsun.com/projects/create-project) > and the main [Getting started guide](https://developer.upsun.com/docs/get-started/here). > They provide all the core concepts and common commands you need to know before using the following materials. For WordPress to successfully deploy and operate, **after completing the [Getting started guide](https://developer.upsun.com/docs/get-started/here)**, you still need to add some required files and make a few changes to your Upsun Cloud configuration. ## Before you begin You need: > [!NOTE] > > Assumptions > There are many ways you can set up a WordPress site or Upsun Cloud project. > The instructions on this page were designed based on the following assumptions: > > * You are building a Bedrock-based WordPress site using Roots.io [Bedrock boilerplate](https://roots.io/bedrock/). > * You have an existing Bedrock-based codebase or created a new Composer project using `roots/bedrock` during the Getting > started guide. > * You selected PHP as your runtime, and MariaDB as a service during the Getting Started guide. It's also assumed that > while using the Getting Started guide you named the project `myapp`, which you will notice is the top-level key in all configuration below. ## 1. Configure your root location Locate the `web:locations` section and update the root (`/`) location as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' \ web: locations: "/": root: "web" \# The front-controller script to send non-static requests to. passthru: "/wp/index.php" \# Wordpress has multiple roots (wp-admin) so the following is required index: \- "index.php" \# The number of seconds whitelisted (static) content should be cached. expires: 600 scripts: true allow: true rules: ^/composer\\.json: allow: false ^/license\\.txt\$: allow: false ^/readme\\.html\$: allow: false "/wp/wp-content/cache": root: "web/wp/wp-content/cache" scripts: false allow: false "/wp/wp-content/uploads": root: "web/app/uploads" scripts: false allow: false rules: \# Allow access to common static files. '(?\: source: root: "/" type: 'php:\{\{version:php:latest}}' mounts: "web/app/wp-content/cache": source: storage source\_path: "cache" "web/app/uploads": source: storage source\_path: "uploads" ## 3. Install dependencies during the build hook To ensure your Composer dependencies are installed during the [build stage](https://developer.upsun.com/docs/core-concepts/build-deploy.md#the-build), locate the `build:` section (below the `hooks:` section).\ Update the `build:` section as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' ... hooks: build: | set -eux composer install --prefer-dist --optimize-autoloader --apcu-autoloader --no-progress --no-ansi --no-interaction You can adjust the `composer install` command to meet your specific requirements. ## 4. Launch tasks during the deploy hook Once the images for our application have been built, there are a few key tasks that must be completed before our newly-built application can receive requests. These tasks include: * Flushing the object cache, which might have changed between current production and newly deployed changes * Running the WordPress database update procedure, in case core is being updated with the newly deployed changes * Running any due cron jobs To perform these tasks, we'll utilize the [deploy hook](https://developer.upsun.com/docs/core-concepts/build-deploy.md#deploy-steps). Locate the `deploy:` section (below the `build:` section). Update the `deploy:` and `post_deploy:` sections as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' ... hooks: deploy: | set -eux \# Flushes the object cache wp cache flush \# Runs the WordPress database update procedure wp core update-db post\_deploy: | wp cron event run --due-now ## 5. Update App container dependencies Add the wp-cli tool to your application build by locating the `dependencies:` section that is commented out, and updating it as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' dependencies: php: wp-cli/wp-cli-bundle: "^2.4" ## 6. Configure your default route Locate the `routes:` section, and beneath it, the `"https://{default}/":` route. Update the route as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' ... routes: "https\://\{default}/": type: upstream upstream: "\:http" cache: enabled: true cookies: \- '/^wordpress\_\*/' \- '/^wp-\*/' Matching the application name `APP_NAME` with the `upstream` definition `APP_NAME:http` is the most important setting to ensure at this stage. If these strings aren't the same, the WordPress deployment will not succeed. ## 7. Add your crons Under your application configuration you can now add a cron. applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' ... crons: wp-cron: spec: '\*/10 \* \* \* \*' commands: start: wp cron event run --due-now shutdown\_timeout: 600 ## 8. Update `.environment` The CLI generated a `.environment` file during the Getting started guide. Notice it has already created some environment variables for you to connect to your database service. ```bash .environment theme={null} # Set database environment variables export DB_HOST="$MARIADB_HOST" export DB_PORT="$MARIADB_PORT" export DB_PATH="$MARIADB_PATH" export DB_DATABASE="$DB_PATH" export DB_USERNAME="$MARIADB_USERNAME" export DB_PASSWORD="$MARIADB_PASSWORD" export DB_SCHEME="$MARIADB_SCHEME" export DATABASE_URL="${DB_SCHEME}://${DB_USERNAME}:${DB_PASSWORD}@${DB_HOST}:${DB_PORT}/${DB_PATH}" ``` To configure the remaining environment variables that WordPress needs to run smoothly, follow these steps. 1. Open the `.environment` file for editing 2. Add the following at the end of the file: ```bash .environment theme={null} # Routes, URLS, and primary domain export SITE_ROUTES="$(echo "$PLATFORM_ROUTES" | base64 --decode)" export UPSTREAM_URLS="$( echo "$SITE_ROUTES" | jq -r --arg app "$PLATFORM_APPLICATION_NAME" \ 'map_values(select(.type == "upstream" and .upstream == $app)) | keys' )" export DOMAIN_CURRENT_SITE="$( echo "$SITE_ROUTES" | jq -r --arg app "$PLATFORM_APPLICATION_NAME" \ 'map_values(select(.primary == true and .type == "upstream" and .upstream == $app)) | keys | .[0] | if (.[-1:] == "/") then (.[0:-1]) else . end' )" export WP_HOME="${DOMAIN_CURRENT_SITE}" export WP_SITEURL="${WP_HOME}/wp" export WP_DEBUG_LOG="/var/log/app.log" # Uncomment this line if you would like development versions of WordPress on non-production environments. # export WP_ENV="${PLATFORM_ENVIRONMENT_TYPE}" export AUTH_KEY="${PLATFORM_PROJECT_ENTROPY}AUTH_KEY" export SECURE_AUTH_KEY="${PLATFORM_PROJECT_ENTROPY}SECURE_AUTH_KEY" export LOGGED_IN_KEY="${PLATFORM_PROJECT_ENTROPY}LOGGED_IN_KEY" export NONCE_KEY="${PLATFORM_PROJECT_ENTROPY}NONCE_KEY" export AUTH_SALT="${PLATFORM_PROJECT_ENTROPY}AUTH_SALT" export SECURE_AUTH_SALT="${PLATFORM_PROJECT_ENTROPY}SECURE_AUTH_SALT" export LOGGED_IN_SALT="${PLATFORM_PROJECT_ENTROPY}LOGGED_IN_SALT" export NONCE_SALT="${PLATFORM_PROJECT_ENTROPY}NONCE_SALT" ``` ## 9. Commit, Push, and Deploy You can now commit all the changes made to `.upsun/config.yaml` and `.environment` and push to Upsun Cloud. ```bash Terminal theme={null} git add . git commit -m "Add changes to complete my Upsun Cloud configuration" upsun push -y ``` ## 10. Routinely run WP Cron (optional) If your site does not receive enough traffic to ensure [WP Cron jobs](https://developer.wordpress.org/plugins/cron/) run in a timely manner, or your site uses caching heavily such that WP Cron isn't being triggered, you might consider adding a [cron job](https://developer.upsun.com/docs/configure-apps/image-properties/crons.md) to your project's configuration to have WP CLI run those scheduled tasks on a routine basis. To do so, locate the `crons:` section that is commented out, and update it as follows: applications: \: source: root: "/" type: 'php:\{\{version:php:latest}}' crons: wp-cron: spec: '\*/15 \* \* \* \*' commands: start: wp cron event run --due-now shutdown\_timeout: 600 The above example will trigger the wp-cli every 15th minute to run WP Cron tasks that are due. Feel free to adjust based on your individual requirements. > [!NOTE] > > When uncommenting, pay attention to the indentation and make sure that the `crons` key aligns with other sibling keys (e.g. `hooks`, `dependencies`, etc.) ## Further resources * [All example files (`.environment`, `.upsun/config.yaml`)](https://github.com/upsun/snippets/tree/main/examples/wordpress-bedrock) ### Documentation * [PHP documentation](https://developer.upsun.com/docs/languages/php) * [Extensions](https://developer.upsun.com/docs/languages/php/extensions.md) * [Performance tuning](https://developer.upsun.com/docs/languages/php/tuning.md) * [PHP-FPM sizing](https://developer.upsun.com/docs/languages/php/fpm.md) * [Authenticated Composer](https://developer.upsun.com/docs/languages/php/composer-auth.md) ### Community content * [PHP topics](https://support.platform.sh/hc/en-us/search?utf8=%E2%9C%93\&query=php) * [WordPress topics](https://support.platform.sh/hc/en-us/search?utf8=%E2%9C%93\&query=wordpress) ### Blogs * [To Upsun, a WordPress migration story](https://upsun.com/blog/to-upsun-a-wordpress-migration-story/) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.