- Issue created by @fmb
- 🇺🇸United States rfay Palisade, CO, USA
Hi - DDEV maintainer here. I took a look, and there is no instance of DDEV_URL at this point in DDEV core, and there hasn't been for a year or two, but there used to be an instance of that in the GitHub Codespaces setup for DDEV.
I searched the entire DDEV org on github and didn't come up with anything. But I imagine you'll find out what's happening if you `grep -r DDEV_URL .ddev` in your project directory.
- 🇺🇸United States rfay Palisade, CO, USA
There shouldn't be a `~/.ddev/docker-composer.chromedriver.yaml` at all (that ~ means your home directory) but you may have a `.ddev/docker-compose.chromedriver.yaml` (not `docker-composer.chromedriver.yaml`).
There is also not a .ddev directory provided by this project. And there are no yaml files in this project.
So something about your setup is the problem.
I do find a reference to docker-compose.chromedriver.yaml in https://github.com/ddev/ddev-contrib/blob/41113f04f060177002de4a7b64086f... - you probably somehow had that obsolete recipe in your world somehow.
As it says there, "**The recommended approach for running tests that require ChromeDriver is to use [ddev-selenium-standalone-chrome add-on](https://github.com/ddev/ddev-selenium-standalone-chrome) instead.**"
- 🇫🇷France fmb Perpinyà, Catalonia, EU
Wow, thanks a lot Randy for passing by here! Much appreciated.
I am sorry I did not give enough details. The main module is here, but the platform is on gitlab.com. We are talking about this file.
- 🇺🇸United States rfay Palisade, CO, USA
I don't know what `com.ddev.app-url` might have been used for, but I imagine it can be removed. It's not a required label (https://ddev.readthedocs.io/en/stable/users/extend/custom-compose-files/...)
In passing, note that the docker-compose.chromedriver.yaml there can only be used on AMD64 machines, so leaves out lots of local development environments. It would be better to remove that and refactor slightly to use `ddev add-on get https://github.com/ddev/ddev-selenium-standalone-chrome`
- 🇫🇷France fmb Perpinyà, Catalonia, EU
It turns out that docker-compose.chromedriver.yaml is not actually needed by anybody working on the project, so I removed it.
Automatically closed - issue fixed for 2 weeks with no activity.