README

1. Create a free trial:

   Register for a 30 day free trial with Platform.sh. When you have completed signup, select the Create from scratch project option. Give you project a name, and select a region where you would like it to be deployed. As for the Production environment option, make sure to match it to this repository's settings, or to what you have updated the default branch to locally.

2. Install the Platform.sh CLI

   Linux/OSX

   curl -sS https://platform.sh/cli/installer | php

   Windows

   curl -f https://platform.sh/cli/installer -o cli-installer.php
   php cli-installer.php

   You can verify the installation by logging in (platformsh login) and listing your projects (platform project:list).

3. Create the repository

   Create a new repository on Bitbucket, set it as a new remote for your local copy, and push to the default branch.

4. Setup the integration:

   Consult the Bitbucket integration documentation to finish connecting a repository to a project on Platform.sh. You will need to create an Access token on Bitbucket to do so.

ddev provides an integration with Platform.sh that makes it simple to develop Drupal locally. Check the providers documentation for the most up-to-date information.

In general, the steps are as follows:

1. Install ddev.
2. A configuration file has already been provided at .ddev/providers/platform.yaml, so you should not need to run ddev config.
3. Retrieve an API token for your organization via the management console.
4. Update your dedev global configuration file to use the token you've just retrieved:

   web_environment:
   - PLATFORMSH_CLI_TOKEN=abcdeyourtoken`

5. Run ddev restart.
6. Get your project ID with platform project:info. If you have not already connected your local repo with the project (as is the case with a source integration, by default), you can run platform project:list to locate the project ID, and platform project:set-remote PROJECT_ID to configure Platform.sh locally.
7. Update the .ddev/providers/platform.yaml file for your current setup:

   environment_variables:
   project_id: PROJECT_ID
   environment: CURRENT_ENVIRONMENT
   application: drupal

8. Get the current environment's data with ddev pull platform.
9. When you have finished with your work, run ddev stop and ddev poweroff.

Lando supports PHP applications configured to run on Platform.sh, and pulls from the same container registry Platform.sh uses on your remote environments during your local builds through its own recipe and plugin.

1. Install Lando.
2. Make sure Docker is already running - Lando will attempt to start Docker for you, but it's best to have it running in the background before beginning.
3. Start your apps and services with the command lando start.
4. To get up-to-date data from your Platform.sh environment (services and mounts), run the command lando pull.
5. If at any time you have updated your Platform.sh configuration files, run the command lando rebuild.
6. When you have finished with your work, run lando stop and lando poweroff.

1. Create a free trial:

   Register for a 30 day free trial with Platform.sh. When you have completed signup, select the Create from scratch project option. Give you project a name, and select a region where you would like it to be deployed. As for the Production environment option, make sure to match it to this repository's settings, or to what you have updated the default branch to locally.

2. Install the Platform.sh CLI

   Linux/OSX

   curl -sS https://platform.sh/cli/installer | php

   You can verify the installation by logging in (platformsh login) and listing your projects (platform project:list).

3. Set the project remote

   Find your PROJECT_ID by running the command platform project:list

   +---------------+------------------------------------+------------------+---------------------------------+
   | ID            | Title                              | Region           | Organization                    |
   +---------------+------------------------------------+------------------+---------------------------------+
   | PROJECT_ID    | Your Project Name                  | xx-5.platform.sh | your-username                   |
   +---------------+------------------------------------+------------------+---------------------------------+

   Then from within your local copy, run the command platform project:set-remote PROJECT_ID.

4. Push

   git push platform DEFAULT_BRANCH

1. Create a free trial:

   Register for a 30 day free trial with Platform.sh. When you have completed signup, select the Create from scratch project option. Give you project a name, and select a region where you would like it to be deployed. As for the Production environment option, make sure to match it to whatever you have set at https://YOUR_NAMESPACE/nextjs-drupal.

2. Install the Platform.sh CLI

   Linux/OSX

   curl -sS https://platform.sh/cli/installer | php

   Windows

   curl -f https://platform.sh/cli/installer -o cli-installer.php
   php cli-installer.php

   You can verify the installation by logging in (platformsh login) and listing your projects (platform project:list).

3. Setup the integration:

   Consult the GitHub integration documentation to finish connecting your repository to a project on Platform.sh. You will need to create an Access token on GitHub to do so.

1. Create a free trial:

   Register for a 30 day free trial with Platform.sh. When you have completed signup, select the Create from scratch project option. Give you project a name, and select a region where you would like it to be deployed. As for the Production environment option, make sure to match it to this repository's settings, or to what you have updated the default branch to locally.

2. Install the Platform.sh CLI

   Linux/OSX

   curl -sS https://platform.sh/cli/installer | php

   You can verify the installation by logging in (platformsh login) and listing your projects (platform project:list).

3. Create the repository

   Create a new repository on GitLab, set it as a new remote for your local copy, and push to the default branch.

4. Setup the integration:

   Consult the GitLab integration documentation to finish connecting a repository to a project on Platform.sh. You will need to create an Access token on GitLab to do so.

1. Create a free trial:

   Register for a 30 day free trial with Platform.sh. When you have completed signup, select the Create from scratch project option. Give you project a name, and select a region where you would like it to be deployed. As for the Production environment option, make sure to match it to this repository's settings, or to what you have updated the default branch to locally.

2. Install the Platform.sh CLI

   Linux/OSX

   curl -sS https://platform.sh/cli/installer | php

   Windows

   curl -f https://platform.sh/cli/installer -o cli-installer.php
   php cli-installer.php

   You can verify the installation by logging in (platformsh login) and listing your projects (platform project:list).

3. Create the repository

   Create a new repository on Bitbucket, set it as a new remote for your local copy, and push to the default branch.

4. Setup the integration:

   Consult the Bitbucket integration documentation to finish connecting a repository to a project on Platform.sh. You will need to create an Access token on Bitbucket to do so.

First, obtain a database dump from your current site and save your dump file as database.sql. Then, import the database into your Platform.sh site using the CLI:

platform sql -e main < database.sql

You first need to download your files from your current hosting environment. The easiest way is likely with rsync, but consult your old host's documentation.

The platform mount:upload command provides a straightforward way to upload an entire directory to your site at once to a mount defined in a .platform.app.yaml file. Under the hood, it uses an SSH tunnel and rsync, so it is as efficient as possible. (There is also a platform mount:download command you can use to download files later.) Run the following from your local Git repository root (modifying the --source path if needed and setting BRANCH_NAME to the branch you are using).

A few examples are listed below, but repeat for all directories that contain data you would like to migrate.

$ platform mount:upload -e main --mount web/sites/default/files --source ./web/sites/default/files
$ platform mount:upload -e main --mount private --source ./private

Note that rsync is picky about its trailing slashes, so be sure to include those.

After the environment has finished its deployment, you can investigate issues that occured on startup, deploy and post_deploy hooks, and generally at runtime using the CLI. Run the command:

platform ssh

If you are running the command outside of a local copy of the project, you will need to include the -p (project) and/or -e (environment) flags as well. Once you have connected to the container, logs are available within /var/log/ for you to investigate.

You may run into a database error after installing Drupal on your production environment initially. To fix, SSH into the application container (platform ssh) and rebuild the cache using Drush:

drush cache-rebuild

Drupal's default settings set hash_salt to an empty string:

$settings['hash_salt'] = '';

In the past, Platform.sh templates have overridden this value:

$settings['hash_salt'] = $settings['hash_salt'] ?? $platformsh->projectEntropy;

This setting was insufficient to cover some user configurations - such as those cases when an application depends on a Null value for hash_salt.

Now, the setting looks like this in settings.platformsh.php:

$settings['hash_salt'] = empty($settings['hash_salt']) ? $platformsh->projectEntropy : $settings['hash_salt'];

This change sets hash_salt to the built-in environment variable PLATFORM_PROJECT_ENTROPY value if the project contains the default settings OR Null. If your application code depends on an empty value, feel free to comment out that line, or reset again later in that file.

Feel free to visit platformsh-templates/drupal9#73 for more details on this discussion.

Platform.sh is a unified, secure, enterprise-grade platform for building, running and scaling web applications. We’re the leader in Fleet Ops: Everything you need to manage your fleet of websites and apps is available from the start. Because infrastructure and workflows are handled from the start, apps just work, so teams can focus on what really matters: making faster changes, collaborating confidently, and scaling responsibly. Whether managing a fleet of ten or ten thousand sites and apps, Platform.sh is the Developer- preferred solution that scales right.

Our key features include:

• GitOps: Git as the source of truth

  Every branch becomes a development environment, and nothing can change without a commit.

• Batteries included: Managed infrastructure

  Simple abstraction in YAML for committing and configuring infrastructure, fully managed patch updates, and 24 runtimes & services that can be added with a single line of code.

• Instant cloning: Branch, merge, repeat

  Reusable builds and automatically inherited production data provide true staging environments - experiment in isolation, test, then destroy or merge.

• FleetOps: Fleet management platform

  Leverage our public API along with custom tools like Source Operations and Activity Scripts to manage thousands of applications - their dependency updates, fresh content, and upstream code.

To find out more, check out the demo below and go to our website.