[Feature]: Support for Non-Sail Docker Containers

[SachinAgarwal1337]

Feature Description

It would be great to get support for non sail docker container.
Currently it is giving error if running via non sail docker container.

[ivanromeroprog]

This will be great! I intend to change these options:

 "Laravel.phpCommand": "docker exec laravelfull-app php \"{code}\"", // The command I use to execute PHP inside the container.  
  "Laravel.basePath": "/var/www", // The base path of my project inside the container.  

This causes the extension not to load, as it appears to be trying to find artisan in the host filesystem.

[piljac1]

This will be great! I intend to change these options:

 "Laravel.phpCommand": "docker exec laravelfull-app php \"{code}\"", // The command I use to execute PHP inside the container.  
  "Laravel.basePath": "/var/www", // The base path of my project inside the container.  

This causes the extension not to load, as it appears to be trying to find artisan in the host filesystem.

The problem is that Laravel.basePath seems to expect a relative path and not an absolute path. Absolute paths should be supported imo, because I think that with your suggested setup (if absolute paths were supported), a non-sail dockerized project would work fine.

[vlauciani]

I'm also using Laravel in a Docker container different from Sail; it would be very useful to be able to specify the absolute path.

In the meantime, I have resolved the issue by creating a symbolic link in my container to the path expected by the package.

[CicerBro]

Using Sail and Cursor.

When I want to click on "home" in this named route redirect()->route('home'); it tries to open /var/www/html/app/Http/Controllers/HomeController.php.

/var/www/html is the path of the code in the Sail container, not on my local machine of course.

[rossminney]

+1 to be able to configure these options to allow for non-sail docker development environments. 🙏

[Orrison]

Bump, this issue leaves the extension unusable for those using their own Docker configuration rather than Sail.

[flowerwOw0316]

It is highly recommended to add this feature, allowing the phpCommand to point directly to the PHP environment within the container. Additionally, the file paths could be converted to their corresponding addresses inside the container. You could even implement this functionality using path mapping, such as:

Host machine address: Container address
{
  c:\\abc\hello-world:/var/www/hello-world
}

This approach would streamline the process and ensure seamless integration between the host machine and the container environment.

[johanvanhelden]

Another bump for visibility - unfortunately this makes the extension unusable for custom Docker setups.

[SirFaenor]

Inspired by this comment #129 (comment) I managed to get it somehow working via a script like this

#!/bin/bash
input_command="$@"

# Replace generic path with your vscode project location
modified_command=$(echo "$input_command" | sed 's|/path/to/vscode/project|/var/www|g')

# Replace with your executable location
full_command="docker compose exec -t web php $modified_command"

eval "$full_command"

Replace "/var/www" with document root inside container.
In command docker compose exec -t web, web is the name of my php container in docker compose setup.

Then, in setting:

"Laravel.phpCommand": "./laravel-vscode.sh" using your path to script

The only thing that doesn't work is opening the controller binded to a route, probably due to the relative path issue mentioned above.

[ctf0]

we need a path-mapping like the one for xdebug

"pathMappings": {
    "/var/www/html": "${workspaceFolder}"
}

[minhnh94]

I'm also using Laravel in a Docker container different from Sail; it would be very useful to be able to specify the absolute path.

In the meantime, I have resolved the issue by creating a symbolic link in my container to the path expected by the package.

this is the only viable workaround rn. I fixed it by adding this to my laravel dockerfile:
RUN mkdir -p /Users/minhnh/<my project folder on host machine> && ln -s /var/www /Users/minhnh/<my project folder on host machine>

and adding this to Laravel: PHP Command in the extension settings:
docker compose exec <laravel container name> php {code}

works flawlessly for now as if I were using sail.