router_bind_all_interfaces doesn't work if configured in the wrong place

[grummbeer]

Yesterday, I updated ddev to the latest version (from ~1.24.2), and after that, my websites were no longer accessible. Neither from my local machine nor from other (LAN) machines. To make my ddev.sites available for other devices in the local network, the parameter router_bind_all_interfaces was set to true in ~/.ddev/global_config.yaml

XDG_CONFIG_HOME

It takes a while to realize, that the global config dir was changed from ~/.ddev to ~/.config/ddev (XDG_CONFIG_HOME). ddev debug test gaves me the hint.

======== DDEV Global Information ========
XDG_CONFIG_HOME is set to non-default value: '/home/stefan/.config'
Global DDEV dir is /home/stefan/.config/ddev

What exactly does this mean? Is this something special at my side or is this a general change?

If this is a general change, then the docs are dated?

https://github.com/ddev/ddev/blob/main/docs/content/users/configuration/config.md

Global $HOME/.ddev/global_config.yaml settings that can apply to all projects.

Should then be $XDG_CONFIG_HOME/ddev/global_config.yaml?

diagnose

Second thing I noticed while debugging.

The command ddev utility diagnose, tells me, that the *.ddev.sites hosts are resolved to 127.0.0.1, but they do not (in my case).

Network Connectivity
====================
✓ Internet accessible from host
✓ DNS resolves *.ddev.site to 127.0.0.1

My lokal DNS (pdnsd/pihole) points to my LAN-IP 192.168.0.1.

dig *.ddev.site
# ddev.site.              86400   IN      A       192.168.0.1
# ;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)

In fact, others resolve them to 127.0.0.1 and proven the general availability.

dig @8.8.8.8 *.ddev.site
# *.ddev.site.            300     IN      A       127.0.0.1
# ;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)

So, what does the diagnose do here? Is this a general test or should this information reflect my local situation?

Network Connectivity
====================
✓ Internet accessible from host
✓ General DNS resolves *.ddev.site to 127.0.0.1
  ^^^^^^^
✓ Local DNS resolves *.ddev.site to 192.168.0.1
  ^^^^^

Thanks and have a nice day.

[grummbeer]

wait :-)

general change?

It is. Since 2022. See commit 5b0e640

docs "architecture/global files"

There’s only one global .ddev directory, which normally lives in your home directory: ~/.ddev ($HOME/.ddev) or in ~/.config/ddev. ~/.ddev takes precedence if it exists, unless $XDG_CONFIG_HOME is set, in which case it will be $XDG_CONFIG_HOME/ddev.

This is weird, means my XDG_CONFIG_HOME was not set before the update yesterday?

Does it make sense to leave a hint/link to"architecture/global files" at "config options", to make the users aware that $HOME/.ddev is not in every case the right path?

[rfay]

Maybe you can do a review of the open

• fix: check for multiple global config dirs on ddev start and improve usage for ~/.ddev in the docs, fixes #7582 #7859

and see if it would have helped you.

[rfay]

Have you solved the problem now?

It seems there's a bug in ddev debug diagnose, could you open a specific issue or PR about fixing it?

[grummbeer]

OK, I will give it a try.

#7871

[grummbeer]

Hey randy thanks for your answer and the fantastic ddev.

Have you solved the problem now?

Yes i already did. Now using $XDG_CONFIG_HOME/ddev instead of $HOME/.ddev. I was just confused and my point was/is more docs related, which is addressed with #7859

[rfay]

Thanks!