Problem/Motivation

The dev repo includes a project name in the DDEV config. This can be annoying if you have multiple instances of the repo locally. On multiple occasions I have accidentally clobbered instances of a site after doing a git reset and forgetting to change the name back.

The name isn't required, and I don't think there is any reason it needs to be included here?

Comments

pameeela created an issue.

rajab natshah’s picture

Hopping to have this for easier local development, testing workflow
#3486786: Allow multiple local ddev builds

Adam commented back to me on this
https://www.drupal.org/project/drupal_cms/issues/3486786#comment-15852543

Managed with number of local dev and tests with
sed -i '1d' .ddev/config.yaml for now

Trying to replicate what Tugboat is doing in my local

Exmaple:

mkdir ~/test
cd ~/test
git clone git@git.drupal.org:project/drupal_cms.git drupal_cms1test3
cd drupal_cms1test3
wget https://git.drupalcode.org/project/drupal_cms/-/merge_requests/182.diff
git apply 182.diff
rm 182.diff
sed -i '1d' .ddev/config.yaml
ddev start
ddev drush site:install --debug
ddev launch
penyaskito’s picture

The fix is trivial, just remove name: drupal-cms-dev. But it will fallback to whatever folder lives in, which could be a problem if people have work in progress / want to keep their db for whatever reason.

So we have 3 options:

  1. Remove name: drupal-cms-dev and move on.
  2. Remove name: drupal-cms-dev and create a new .ddev/config.sitename.yaml with that name. Might make it easier to override.
  3. Do nothing.

Razor Occam's says 1. But don't want to commit it without verifying at least Pam and @phéna have nothing in flight they care about.

phenaproxima’s picture

Well…that is part of our internal development infrastructure. All of that stuff, as far as I am concerned, has ZERO guarantee of backwards compatibility whatsoever.

Maybe we just do this and post an announcement in Slack in case it affects anyone?

penyaskito’s picture

That should be perfectly fine IMHO.
I agree we want to remove it at some point anyway, now that machines conquered us and they want to work with git worktree and all that magic robots like to do (see https://ddev.com/blog/git-worktree-contributor-training/ for DDEV support)