You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the extension on code-server the preview tries to connect to localhost instead of the proxy url.
Description
It would be nice to set the websocket path for the lsp to connect to because automatically getting it seems complex or impossible becasue it is configurable in code-server.
Examples/Questions
Becasue the proxy url can be configured to be a subpath or a subdomain it would be nice to change to either method with a switch (Radio button) and configure it
Localhost
Subdomain
Subpath
Raising questions to highlight the uncertain design for the feature.
### Accessing web services
If you're working on web services and want to access them locally, code-server can proxy to any port using either a subdomain or a subpath, allowing you to securely access these services using code-server's built-in authentication.
###
The text was updated successfully, but these errors were encountered:
You can write add a shim for websocket connection to preview over the internet.
Last month I had solved this problem for gitpod (code-server-like web service).
I am happy to help you write code on your hand. Ask me anything 😉
Describe the bug
When using the extension on code-server the preview tries to connect to localhost instead of the proxy url.
Description
It would be nice to set the websocket path for the lsp to connect to because automatically getting it seems complex or impossible becasue it is configurable in code-server.
Examples/Questions
Package/Software version:
code-server version(Help -> About):
docker image: codercom/code-server:4.93.1-ubuntu
tinymist extension version:
v0.11.22
. Get it bytinymist --version
in terminal.as bundeled with the extension of this version
Logs:
tinymist server log(Output Panel -> tinymist):
tinymist client log(Help -> Toggle Developer Tools -> Console):
Additional context
code.domain.tld
code.domain.tld/proxy/<port>
The text was updated successfully, but these errors were encountered: