Support multiple environments with one provider configuration

[dahaupt]

Currently we have two remote environments: Staging and Production. We run the project on a shared hosting server (powered by Plesk). The two environments are simply located in two different directories.

Based on the current documentation we created two provider configurations to pull both environments with ddev pull. The only difference between the two configuration files (staging.yaml and production.yaml) is the environment variable projectRoot.

Therefore, in our case it would be great if this could be implemented with only one provider configuration (e.g. only plesk.yaml or remote.yaml).

Suggestion:

ddev pull plesk --env=staging

plesk.yaml:

environment_variables:
  phpBin: /opt/plesk/php/7.4/bin/php
 
environments:
  staging:
    projectRoot: /path/to/staging/project/
  production:
    projectRoot: /path/to/production/project/

db_pull_command:
  command: |
    # set -x   # You can enable bash debugging output by uncommenting
    set -eu -o pipefail
    # Fetch database with variable ${projectRoot} provided by enviroment configuration
  service: web

Looking forward to your feedback!

[rfay]

Unfortunately the logic for the pull is implemented in the golang code, and it doesn't anticipate this. You could easily implement it as a custom web command though, you've already done the work, and then you'd be in control of the logic and be perfectly happy.

[rfay]

Another case where the existing pull logic is unsatiisfactory is multisite, and there are a couple of workarounds. But this stack overflow shows how to turn pull logic into a custom command, almost the same thing. Also related,

• Make more robust and flexible options for how importing works in ddev pull #3223

[dahaupt]

@fray Thanks for your reply!

We are already looking forward to #3223, since we would like to rsync our assets directly with the directory of assets in TYPO3 (public/fileadmin/), which would be way faster than always downloading all files.

Unfortunately the logic for the pull is implemented in the golang code, and it doesn't anticipate this.

Do I understand you correctly that a change is therefore not possible? Or could we implement support for multiple environments if there was general support for the idea?

Otherwise, I would stick to your suggested approach using a custom command!

[rfay]

No, I'm saying that we can absolutely improve the logic via #3223 - we're not stuck where we are. Just saying that I don't know how to do what you're wanting here with the current implementation. But can be done with a custom command.