Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mount point in local file system #103

Closed
tanc opened this issue Feb 11, 2019 · 4 comments
Closed

Mount point in local file system #103

tanc opened this issue Feb 11, 2019 · 4 comments
Labels
duplicate This issue or pull request already exists wontfix This will not be worked on

Comments

@tanc
Copy link

tanc commented Feb 11, 2019

I'm currently trying a particularly mind bending xdebug set up with VSCode where I have a server (local network) which runs a set of Docker containers, inside of which PHP and xdebug (with Apache serving) are running. On my laptop I'm viewing the site in my browser and triggering xdebug inside the containers. Also on my laptop I have mounted the server's files through this extension (sshfs).

This is almost working for me but I'm having trouble mapping the file paths. When xdebug triggers on an error I'm seeing file not found messages like this:

screenshot of problem

Where does this extension mount the workspace on the local machine?

Currently my debug config for path mapping is:

      "pathMappings": {
        "/app/web": "${workspaceRoot}/web"
      }

This should be correctly mapping the path within the container (where xdebug is running) to the workspace but isn't working as shown in the screenshot above.

Maybe I need to be more explicit in my path mapping for the local part? Instead of ${workspaceRoot} use the full path to the mount point for example.

@tanc
Copy link
Author

tanc commented Feb 11, 2019

I've just tried to specify ssh:// like:

      "pathMappings": {
        "/app/web": "ssh://iucnflr/web"
      }

But this results in file:// being prepended:

screenshot showing file:// prepended

@SchoofsKelvin
Copy link
Owner

The extension doesn't mound the workspace anywhere on the local machine. All files/directories are saved/read over the SSH connection. VSCode keeps track of which files are open, caching directory entries, ... it only asks the extension to read/write directories/files.

Lots of extensions don't support non-local file systems right now. See #42 for more information.

@SchoofsKelvin SchoofsKelvin added duplicate This issue or pull request already exists wontfix This will not be worked on labels Feb 11, 2019
@tanc
Copy link
Author

tanc commented Feb 11, 2019

Thank you, I had a feeling it would be the extensions problem. Will open an issue with them

@SchoofsKelvin
Copy link
Owner

VSCode currently doesn't provide an API to extensions for this, so as far as I know, they can't solve the issue right now. (microsoft/vscode#48034)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants