Changing the theia web path #13464
-
|
Hey there, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hey @UltraBlackLinux, you would usually solve this using some sort of reverse proxy. Both the subdomain and path version work similarly in the sense that they forward to some Note that I would recommend using subdomains (assuming you allow users to install vscode extensions via the registry view) as otherwise all webviews become security hazards - each vscode extension could potentially read the localStorage/cookie storage of other extensions. |
Beta Was this translation helpful? Give feedback.
-
|
well I already figured it out and forgot to close this. Theia is the program that has caused me the least problems in this regard EVER. It has worked straight out of the box without saying a thing. Great tool. |
Beta Was this translation helpful? Give feedback.
-
Hello, how did you solve it? Do you have any relevant documents or cases?@UltraBlackLinux |
Beta Was this translation helpful? Give feedback.
-
|
I literally forgot lol. All I know now is that I switched to the vscode server some time later because the plugin handling on theia got really really annoying. |
Beta Was this translation helpful? Give feedback.
-
haha😄 |
Beta Was this translation helpful? Give feedback.
Hey @UltraBlackLinux,
you would usually solve this using some sort of reverse proxy. Both the subdomain and path version work similarly in the sense that they forward to some
localhost:<port>address on the container that is used to run Theia. See also theia-cloud.Note that I would recommend using subdomains (assuming you allow users to install vscode extensions via the registry view) as otherwise all webviews become security hazards - each vscode extension could potentially read the localStorage/cookie storage of other extensions.