[Feature]: Support `ddev` environment

[jonagoldman]

Feature Description

Support for ddev will be really appreciated.

[theteknocat]

Plus one on this.

It's not really usable with ddev as it just keeps producing errors like this:

__VSCODE_LARAVEL_STARTUP_ERROR__: require(/var/www/html/routes/breadcrumbs.php): Failed to open stream: No such file or directory

[theteknocat]

And I see the source of the specific error I'm having. The Laravel config cache file in bootstrap/cache/config.php has full paths to the file system root. Since the cache is generated within the ddev environment that of course makes sense.

The Laravel extension of course runs outside the ddev environment and yet is attempting to load things with these paths, so of course it doesn't work. As a short-term workaround, I'll try creating a symlink link in /var/www that points to the Laravel app I'm currently working on, but of course that's only a temp solution and can only work for one app at a time.

[theteknocat]

I've worked around this for now by having a wrapper script to run php, which I use for other extensions as well. It will call php via ddev and modify any arguments containing the current directory path to work within the ddev environment. Then I just configure the extension to use this as the php binary.

#!/bin/bash

current_dir=$(pwd)

# If the $current_dir ends with "/.ddev" then we need to remove the ".ddev".
if [[ $current_dir == */.ddev ]]; then
  current_dir=${current_dir%/.ddev}
fi

# Loop through all the arguments and replace any part of any argument that
# matches current_dir with /var/www/html. This is necessary because the vscode
# extension will pass in a full path to the file on the local system, rather
# than the path to the file inside the ddev container.
for i in "$@"
do
  if [[ $i =~ $current_dir ]]; then
    new_arg=$(echo "$i" | sed "s#$current_dir#/var/www/html#")
    # Replace the argument in the list of arguments
    set -- "${@/$i/$new_arg}"
  fi
done

ddev exec php "$@"

This works quite well, though I find this extension sometimes takes a very long time to run - not sure if it is related to using this wrapper script or that's just an issue with the extension itself - so it will sometimes time out and produce an error. When I view the error, there's no actual error message, just a bunch of json output that's cut short. Maybe this is due to making a lot of edits and saving frequently before it's finished checking the file after the previous save.

[damms005]

Hey guys, incoming... #398