Install drops-7 with Composer on Pantheon.
This package is auto-updated.
Last update: 2022-08-08 23:03:47 UTC
This repository can be used to set up a Composer-Managed Drupal 7 site on Pantheon.
This repository is a start state for a Composer-based Drupal 7 workflow with Pantheon. It is meant to be copied by the the Terminus Build Tools Plugin which will set up for you a brand new
- GitHub repo
- Free Pantheon sandbox site
- A CircleCI configuration to run tests and push from the source repo (GitHub) to Pantheon.
For more background information on this style of workflow, see the Pantheon documentation.
Before running the
terminus build:project:create command, make sure you have all of the prerequisites:
- A Pantheon account
- Terminus, the Pantheon command line tool
- The Terminus Build Tools Plugin
- An account with GitHub and an authentication token capable of creating new repos.
- An account with CircleCI and an authentication token.
You may find it easier to export the GitHub and CircleCI tokens as variables on your command line where the Build Tools Plugin can detect them automatically:
export GITHUB_TOKEN=[REDACTED] export CIRCLE_TOKEN=[REDACTED]
Once you have all of the prerequisites in place, you can create your copy of this repo with one command:
terminus build:project:create pantheon-systems/example-drops-7-composer my-new-site --team="Agency Org Name"
The parameters shown here are:
- The name of the source repo,
pantheon-systems/example-drops-7-composer. If you are interest in other source repos like WordPress, see the Terminus Build Tools Plugin.
- The machine name to be used by both the soon-to-be-created Pantheon site and GitHub repo. Change
my-new-siteto something meaningful for you.
--teamflag is optional and refers to a Pantheon organization. Pantheon organizations are often web development agencies or Universities. Setting this parameter causes the newly created site to go within the given organization. Run the Terminus command
terminus org:listto see the organizations you are a member of. There might not be any.
Pantheon will serve the site from the
/web subdirectory due to the configuration in
pantheon.yml, facilitating a Composer based workflow. Having your website in this subdirectory also allows for tests, scripts, and other files related to your project to be stored in your repo without polluting your web document root.
One of the directories moved to the git root is
/config. This directory holds Drupal's
.yml configuration files. In more traditional repo structure these files would live at
/sites/default/config/. Thanks to this line in
settings.php, the config is moved entirely outside of the web root.
If you are just browsing this repository on GitHub, you may notice that the files of Drupal core itself are not included in this repo. That is because Drupal core and contrib modules are installed via Composer and ignored in the
.gitignore file. Specific contrib modules are added to the project via
composer.lock keeps track of the exact version of each modules (or other dependency). Modules, and themes are placed in the correct directories thanks to the
"installer-paths" section of
composer.json also includes instructions for
drupal-scaffold which takes care of placing some individual files in the correct places like
So that CircleCI will have some test to run, this repository includes a configuration of Behat tests. You can add your own
.feature files within
If you need to enable Github Actions for an existing project, you should copy .ci/.github to .github and then add the following secrets to Github Actions configuration:
When using this repository to manage your Drupal site, you will no longer use the Pantheon dashboard to update your Drupal version. Instead, you will manage your updates using Composer. Ensure your site is in Git mode, clone it locally, and then run composer commands from there. Commit and push your files back up to Pantheon as usual.