Hello,
My remote server has a 'www' symlink to the standard 'public_html' folder. This otherwise excellent extension to VSCode doesn't "see" this symlink properly. Is there a way to bypass/fix this?
I have different projects that are (each) locally on a 'www' folder (and remotely also on 'www', with 'www' on the remote symlinked to 'public_html'). Other programs have no problem in syncing the local 'www' folder to the remote 'public_html' folder, using the symlink on the remote server correctly. Renaming the local folders from 'www' to 'public_html' is a possibility, of course, but I'd rather not go down this path since (among other reasons) it's not a real fix.
Any help/suggestions gratefully appreciated.
Hello, My remote server has a 'www' symlink to the standard 'public_html' folder. This otherwise excellent extension to VSCode doesn't "see" this symlink properly. Is there a way to bypass/fix this? I have different projects that are (each) locally on a 'www' folder (and remotely also on 'www', with 'www' on the remote symlinked to 'public_html'). Other programs have no problem in syncing the local 'www' folder to the remote 'public_html' folder, using the symlink on the remote server correctly. Renaming the local folders from 'www' to 'public_html' is a possibility, of course, but I'd rather not go down this path since (among other reasons) it's not a real fix. Any help/suggestions gratefully appreciated.