Skip to content
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

Use custom module name in symlink-project, different from DDEV_SITENAME #74

Open
donquixote opened this issue Sep 11, 2024 · 0 comments

Comments

@donquixote
Copy link
Contributor

I have this situation where the ddev project/site name is different from the desired module name.

Currently the project name is like "something-drupal" whereas the module name should be like "something_banana".
So the symlinks should go to web/modules/custom/something_banana and not web/modules/custom/something_drupal.
What makes this relevant is that the project contains hard-coded paths which assume a directory name.
(Let's not go into detail about how the problems with my setup are a bit silly. It's an existing project.)

A less silly case could be if we want to have 2 instances in 2 separate dirs for the same project.
So one would be something the other would be something-1.
Currently, symlink-project would create web/modules/custom/something in one project dir, and web/modules/custom/something_1 in the other project dir.

Would it make sense to decouple the module dir name from the DDEV_SITENAME env variable?

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

No branches or pull requests

1 participant