Problem/Motivation

Currently DrupalPod requires setting up environment variables via GitPod URL. If using DrupalPod locally, one has to replicate these environment variables manually.

It would be nice if there was a pattern like dotenv that would source environment variables from a local file from the script.

DP_EXTRA_DEVEL
DP_EXTRA_ADMIN_TOOLBAR
DP_CORE_VERSION
DP_PROJECT_NAME
DP_PROJECT_TYPE
DP_INSTALL_PROFILE
DP_MODULE_VERSION
DP_ISSUE_FORK
DP_ISSUE_BRANCH
DP_PATCH_FILE (we should deprecate this)

GITPOD_REPO_ROOT (could be set via pwd)

Steps to reproduce

Proposed resolution

Source environment variables populated from a file?

Remaining tasks

User interface changes

API changes

Data model changes

Comments

mradcliffe created an issue. See original summary.

rfay’s picture

You can certainly use `.ddev/.env` in gitpod/drupalpod.

mradcliffe’s picture

It would need to source env vars that are used in .gitpod/drupal scripts, not ddev itself.

mradcliffe’s picture

Issue summary: View changes