Skip to content

Add DDEV Configuration#32

Open
bhanu951 wants to merge 7 commits into
joachim-n:mainfrom
bhanu951:feature/make-ddev-compatible
Open

Add DDEV Configuration#32
bhanu951 wants to merge 7 commits into
joachim-n:mainfrom
bhanu951:feature/make-ddev-compatible

Conversation

@bhanu951

Copy link
Copy Markdown
Contributor

No description provided.

Comment thread README.md

## Core Development Using DDEV

1. Clone this repository by using `git clone --branch=master https://github.com/bhanu951/drupal-core-development-project.git`

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line needs update based upon this PR.

@rfay rfay left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be based on a very old DDEV configuration. Please do a ddev config --auto and look at the result and use that.

I would prefer that the many custom commands like nightwatch and phpcs come from one of the other add-ons which is carefully maintained, to avoid conflicts, but understand the convenience of using them here.

Thanks for the effort, please update to current usage, thanks!

Comment thread .ddev/config.yaml Outdated
Comment thread .ddev/config.yaml
router_https_port: "443"
xdebug_enabled: false
additional_hostnames:
- drupal-core-testing

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this here means you'll have trouble running more than one project at a time.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, but it makes easier to access phpunit tests output htmls.

Comment thread .ddev/config.yaml Outdated
Comment thread .ddev/config.yaml Outdated
Comment thread .ddev/config.yaml Outdated
Comment thread .ddev/config.yaml Outdated
Comment thread .ddev/config.yaml Outdated
Comment thread .vscode/launch.json Outdated
Comment thread .ddev/commands/web/README.txt Outdated
Comment thread .ddev/docker-compose.override.yaml Outdated
@@ -0,0 +1,11 @@
#
# This file can be used for overriding ENV variables.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please put environment variables in the config.yaml (web_environment) instead of this file. Remove this file.

@bhanu951 bhanu951 Oct 31, 2024

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think having a separate file makes it's easier for modification. But will remove the file from PR

@joachim-n

Copy link
Copy Markdown
Owner

@rfay I was just saying in Slack most of this looks like it belongs in the DDEV for core-dev add-on instead :)

@bhanu951 bhanu951 changed the title Make DDEV Compatible. Add DDEV Configuration Oct 31, 2024
@bhanu951

Copy link
Copy Markdown
Contributor Author

This seems to be based on a very old DDEV configuration.

Yup was using it from long time havent updated it recently , ran ddev config --auto and updated config.yml .

I would prefer that the many custom commands like nightwatch and phpcs come from one of the other add-ons which is carefully maintained, to avoid conflicts, but understand the convenience of using them here.

I like to have them in this repo itself which makes all the required tools for core development available at one place.

@rfay updated the PR with suggested changes please have a look into it again.

To jog your memory to recall earlier discussion old PR of same changes

#16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants