Support for Pantheon Websites

This guide will show you how to connect to Pantheon websites. Be aware that you do not install Loft Deploy on the remote server; you will use Pantheon's Terminus instead.

Install Terminus

Install with Composer at the same level as you installed Loft Deploy, e.g. composer require pantheon-systems/terminus
Check installation using loft_deploy.sh configtest

Configure Terminus

You must have something like the following in config.yml on your local dev machine for the production section:

production:
  files:
  - code/sites/default/files
  - code/sites/default/files/private
  pantheon:
    uuid: UUID-GOES-HERE
    site: SITE_NAME
    machine_token: 'MACHINE_TOKEN_HERE'

Configure exclude files

Pantheon includes the private files directory inside of the public files directory. You will want to exclude the private directory by adding the following lines to files_exclude.txt:

    private

Then you should set up the second array element as files/private as shown above and then that will transfer your private directory, if you so desire.

Configuration Hints

To obtain or get more info about machine tokens.
You can determine the site name by using ldp terminus site:list after first authenticating.

Test installation

Then run configtest to see if Terminus is installed correctly.
You may want to clearcache as a first step in debugging.

Usage

Authenticate using the Loft Deploy credentials with the following:
```
ldp terminus site:list
```

Files

@todo This must be updated with the new YAML format:

(Terminus is not necessary for files support at this time.)
Connection info is found in the dashboard.

The following must appear in your dev config file:

production_server='$ENV.$SITE@appserver.$ENV.$SITE.drush.in'
production_port=2222
production_files='files'
pantheon_live_uuid=''

More reading: https://pantheon.io/docs/rsync-and-sftp/