-
Notifications
You must be signed in to change notification settings - Fork 19
Lando #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Lando #109
Conversation
…courage use of yarn instead of npm
Add mannequin service
…. Move environment config from docker directory to .env
…lando tooling for importing from pantheon
…ire-agent` is always running.
Blackfire in Lando (alternate approach)
rbayliss
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments below. The big one is the rename of the .env directory to .lando (or something else). In general, this PR takes us halfway - it gets Lando set up for local development, but still runs docker-compose in CircleCI. That's ok - I think it'd be fine to figure out Lando in circle as a future step.
| echo " | ||
| Refresh your local environment from Pantheon. | ||
| Options: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this file needed anymore? We can just use lando pull now, right?
| # * TERMINUS_MACHINE_TOKEN | ||
| # | ||
| # It also depends on the following environment variables declared in docker/drupal.env: | ||
| # It also depends on the following environment variables declared in .env/drupal.env: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should use .env as a directory, because it prevents us from ever using a .env file. In #111, we discussed moving this into .lando instead.
| # | ||
| # * TERMINUS_SITE | ||
| # * TERMINUS_SOURCE_ENVIRONMENT | ||
| # * TERMINUS_ENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a compelling reason to rename this variable? If not, I'd prefer to leave it as TERMINUS_SOURCE_ENVIRONMENT for backward compatibility reasons.
| @@ -0,0 +1,12 @@ | |||
| <?php | |||
|
|
|||
| $databases['default']['default'] = array ( | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know these are the lando defaults, but for flexibility, I think we should use this instead:
$lando_info = json_decode(getenv('LANDO_INFO'), TRUE);
$databases['default']['default'] = [
'driver' => 'mysql',
'database' => $lando_info['database']['creds']['database'],
'username' => $lando_info['database']['creds']['user'],
'password' => $lando_info['database']['creds']['password'],
'host' => $lando_info['database']['internal_connection']['host'],
'port' => $lando_info['database']['internal_connection']['port'],
];
This will support changing credentials through Lando.
No description provided.