Document proxy and shortcomings

I have spent my whole day wo research and find out how I can deploy a Cloud IDE instance for vue development environment. I found out that /absproxy works very differently from /proxy which the documentation didn’t mentioned about a lot. Another problem was the sockjs-node, I have looked up these issues and prs to find out more clues:

• #2674
• #2222
• #2563

Infact, create-react-app script did fixed the sockjs-node’s always pointing root / issue, meanwhile, there’s no any effective or useful way to make vue/cli3’'s sockjs-node to work.

There is a example that worth vue developers to take a look:

• #3918

In this example, the demo was shown as local development envirnment with no subdirectory, however, it was painful to setup a nginx/Apache reverse proxy server rewrite rule without reading the proxy code of code-server it self (which took the most of my time).

Will there be any documentation to summarize the way those proxy work, and maybe, support vue/sockjs-node proxy in HTTPS development envirnment (HTTPS development envirnment is very important in this age of time)?

[nekomeowww]

I will provide a @vue/cli (Vue3) example and a vite (Vue3) example to help you guys improve the documentation.

[nekomeowww]

I found out that I can’t make vitesse (one of the boilerplate project for vite) work in HTTPS at all, or even with pure vite project without any framework added. This might related to the secured websocket implementation of vite.

Is this true with a subdomain or just the path-based proxy?

Both subdomain and path-based proxy