SiteFarm Pantheon
, (*1)
This repository is a start state for a Composer-based SiteFarm Drupal 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, (*2)
This repository is meant to be copied one-time by the the Terminus Build Tools Plugin but can also be used as a template. It should not be cloned or forked directly., (*3)
The Terminus Build Tools plugin will scaffold a new project, including:, (*4)
- A Git repository
- A free Pantheon sandbox site
- Continuous Integration configuration/credential set up
You will need:
You may find it easier to export the Bitbucket (or GitHub) and CircleCI tokens as variables on your command line where the Build Tools Plugin can detect them automatically:, (*5)
export BITBUCKET_USER=[REDACTED]
export BITBUCKET_PASS=[REDACTED]
# and/or
export GITHUB_TOKEN=[REDACTED]
export CIRCLE_TOKEN=[REDACTED]
Run this one command and watch the magic happen
$ terminus build:project:create ucdavis/sitefarm-pantheon --git=bitbucket --stability=dev --team="University of California Davis" --org=ucdavis my-sitefarm-site
Replace "my-sitefarm-site" would your desired site machine name in Pantheon.
Replace "--org=ucdavis" with your own bitbucket team., (*6)
Once the build is completed, log into Bitbucket and copy the public deploy key from your new repository into the ssh keys for ietwebdev/sitefarm, ietwebdev/sitefarm-theme-one, and ietwebdev/aggiefeed-drupal-module, (*7)
Now, you can clone down the Bitbucket repo and begin work., (*8)
Important files and directories
/web
Pantheon will serve the site from the /web subdirectory due to the configuration in pantheon.yml. This is necessary for 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 or being web accessible from Pantheon. They may still be accessible from your version control project if it is public. See the pantheon.yml documentation for details., (*9)
/config
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., (*10)
/composer.json
This project uses Composer to manage third-party PHP dependencies., (*11)
The require section of composer.json should be used for any dependencies your web project needs, even those that might only be used on non-Live environments. All dependencies in require will be pushed to Pantheon., (*12)
The require-dev section should be used for dependencies that are not a part of the web application but are necessary to build or test the project. Some example are php_codesniffer and phpunit. Dev dependencies will not be deployed to Pantheon., (*13)
If you are just browsing this repository on GitHub, you may not see some of the directories mentioned above. That is because Drupal core and contrib modules are installed via Composer and ignored in the .gitignore file., (*14)
This project uses the following required dependencies:, (*15)
-
composer/installers: Relocates the installation location of certain Composer projects by type; for example, this component allows Drupal modules to be installed to the modules directory rather than vendor., (*16)
-
drupal/core-composer-scaffold: Allows certain necessary files, e.g. index.php, to be copied into the required location at installation time., (*17)
-
drupal/core-recommended: This package contains Drupal itself, including the Drupal scaffold files., (*18)
-
pantheon-systems/drupal-integrations: This package provides additional scaffold files required to install this site on the Pantheon platform. These files do nothing if the site is deployed elsewhere., (*19)
-
drush-ops/behat-drush-endpoint: Used by Behat tests., (*20)
-
rvtraveller/qs-composer-installer: Allows a site to install quicksilver hooks from a Composer package., (*21)
-
zaporylie/composer-drupal-optimizations: This package makes composer update operations run more quickly when updating Drupal and Drupal's dependencies., (*22)
The following optional dependencies are also included as suggestions:, (*23)
-
pantheon-systems/quicksilver-pushback: This component allows commits from the Pantheon Dashboard to be automatically pushed back to GitHub for sites using the Build Tools Workflow. This package does nothing if that workflow has not been set up for this site., (*24)
-
drush/drush: Drush is a commandline tool that provides ways to interact with site maintenance from the command line., (*25)
-
drupal/console: Drupal Console is similar to and an alternative for Drush. You may use either or both., (*26)
-
cweagans/composer-patches: Allows a site to be altered with patch files at installation time., (*27)
-
drupal/config_direct_save: Provides a way to export configuration directly to the filesystem (in SFTP mode) directly from the Drupal admin interface. This is a convenient way to manage configuration files., (*28)
-
drupal/config_installer: Allows a site to be re-installed through the Drupal web installer using existing exported configuration files., (*29)
Any of the optional dependencies may be removed if they are not needed or desired., (*30)
/.ci
This .ci directory is where all of the scripts that run on Continuous Integration are stored. Provider specific configuration files, such as .circle/config.yml and .gitlab-ci.yml, make use of these scripts., (*31)
The scripts are organized into subdirectories of .ci according to their function: build, deploy, or test., (*32)
Build Scripts .ci/build
Steps for building an artifact suitable for deployment. Feel free to add other build scripts here, such as installing Node dependencies, depending on your needs., (*33)
-
.ci/build/php installs PHP dependencies with Composer
Build Scripts .ci/deploy
Scripts for facilitating code deployment to Pantheon., (*34)
-
.ci/deploy/pantheon/create-multidev creates a new Pantheon multidev environment for branches other than the default Git branch
-
.ci/deploy/pantheon/dev-multidev deploys the built artifact to either the Pantheon dev or a multidev environment, depending on the Git branch
Automated Test Scripts .ci/tests
Scripts that run automated tests. Feel free to add or remove scripts here depending on your testing needs., (*35)
Static Testing .ci/test/static and tests/unit
Static tests analyze code without executing it. It is good at detecting syntax error but not functionality., (*36)
Visual Regression Testing .ci/test/visual-regression
Visual regression testing uses a headless browser to take screenshots of web pages and compare them for visual differences., (*37)
-
.ci/test/visual-regression/run Runs BackstopJS visual regression testing.
-
.ci/test/visual-regression/backstopConfig.js The BackstopJS configuration file. Setting here will need to be updated for your project. For example, the pathsToTest variable determines the URLs to test.
Behat Testing .ci/test/behat and tests/behat
Behat is an acceptance/end-to-end testing framework written in PHP. It faciliates testing the fully built Drupal site on Pantheon infrastucture. The Drupal Behat Extension is used to help with integrating Behat and Drupal., (*38)
-
.ci/test/behat/initialize creates a backup of the environment to be tested
-
.ci/test/behat/run sets the BEHAT_PARAMS environment variable with dynamic information necessary for Behat and configure it to use Drush via Terminus and starts headless Chrome, and runs Behat
-
.ci/test/behat/cleanup restores the previously made database backup and saves screenshots taken by Behat
-
tests/behat/behat-pantheon.yml Behat configuration file compatible with running tests against a Pantheon site
-
tests/behat/tests/behat/features Where Behat test files, with the .feature extension, should be stored. The provided example tests will need to be replaced with project specific tests.
-
tests/behat/tests/behat/features/content.feature A Behat test file which logs into the Drupal dashboard, creates nodes, users and terms, and verifies their existience in the Drupal admin interface and the front end of the site
Updating your site
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., (*39)
Wallogit.com
