Testor requires configuration to be set in .testor.yml. It is optional to use the .testor_secret.yml file, which would not be committed to the repository.

Setting up a Remote Server

Establish the connection to the remote server. 

pantheon:
 site: '<Pantheon site name>'

Using an SFTP Server

In .testor.yml, provide the following values below. The password can be in .testor.yml (in which case, don't commit it to the repo) or it can be in .testor_secret.yml.

sftp:
  host: '<host name or IP address>'
  user: '<user>'
  key: 'id_rsa'  # If this is set, the password is for the key. Otherwise, it's for the server.
  password: '<password>' # If you place the password here, do not commit this file to the repo.
  root: 'sftp/upload'    # The root directory.

You can handle the password in one of two ways. If you include it in .testor.yml, as above, do not save the .testor.yml file to the repository.

Alternatively, you can store the password in .testor_secret.yml, thereby allowing you to store .testor.yml in the repository; in this case, do not save .testor_secret.yml in the repository.

# Don't add this to version control.
sftp_password: '<password>'

Or, for better security, keep the password out of any file and export it via setup bash script, like this:

 export ROBO_SFTP_PASSWORD='<secret key>'

Using a S3-compatible Server

In .testor.yml, provide the following values:

s3:
 config:
   version: 'latest'
   region: ''
   endpoint: '<cluster URL>'
   credentials:
     key: '<access key>'
     secret: '<S3 secret>' # If you place the secret here, do not commit this file to the repo.
 bucket: '<bucket name>'

You can handle the secret key in one of two ways. If you include it in .testor.yml, as above, do not save the .testor.yml file to the repository.

Alternatively, you can store the secret in .testor_secret.yml, thereby allowing you to store .testor.yml in the repository; in this case, do not save .testor_secret.yml in the repository.

# Don't add this to version control.
s3_secret: '<secret key>'

Or, for better security, keep the secret out of any file and export it via setup bash script, like this:

 export ROBO_S3_SECRET='<secret key>'