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
Support configuring shared local servers per project #113
Comments
@diminutivesloop Great suggestion! One way we could enable this is via a file (say vslsconfig.json) that would allow you to set per-project/folder settings including this. The file could then be committed to source control as well for use team wide if desired. Would that meet the need in your view? |
I think this would be a great idea! Looking forward this feature :) |
We haven't heard significant demand for this, and we already auto-share servers when you start them, so I'm going to close this enhancement for now. We did the auto-sharing work after this issue was initially filed, and so it would be great to revalidate that we still need it. If so, please feel free to re-open it. Thanks! 👍 |
There were two issues created related to this issue so I'm not going to create another one. This and #3207 they are both closed. The proposed solution doesn't work for me. The live share auto grabbing shared servers sometimes work for web servers but most of the time doesn't work for back end services which I have multiple of. I would love to have the config file or VSCode workspace settings "liveshare.autoForwardedServers" or something like that. |
Some of the projects I develop require sharing multiple local server ports for the guest to successfully access my local instance of the application on their machine. To make this process more straightforward it would be helpful to be able to save a set of shared local servers on a per-project basis that would either be automatically shared or shareable via a single command.
The text was updated successfully, but these errors were encountered: