File tree 1 file changed +22
-0
lines changed
1 file changed +22
-0
lines changed Original file line number Diff line number Diff line change 14
14
- [ Using a subpath] ( #using-a-subpath )
15
15
- [ Stripping ` /proxy/<port> ` from the request path] ( #stripping-proxyport-from-the-request-path )
16
16
- [ Proxying to create a React app] ( #proxying-to-create-a-react-app )
17
+ - [ Proxying to a Vue app] ( #proxying-to-a-vue-app )
17
18
18
19
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
19
20
@@ -348,3 +349,24 @@ You should then be able to visit `https://my-code-server-address.io/absproxy/300
348
349
code-server!
349
350
350
351
> We highly recommend using the subdomain approach instead to avoid this class of issue.
352
+
353
+ ### Proxying to a Vue app
354
+
355
+ Similar to the situation with React apps, you have to make a few modifications to proxy a Vue app.
356
+
357
+ 1 . add ` vue.config.js `
358
+ 2 . update the values to match this (you can use any free port):
359
+
360
+ ``` js
361
+ module .exports = {
362
+ devServer: {
363
+ port: 3454 ,
364
+ sockPath: " sockjs-node" ,
365
+ },
366
+ publicPath: " /absproxy/3454" ,
367
+ }
368
+ ```
369
+
370
+ 3 . access app at ` <code-server-root>/absproxy/3454 ` e.g. ` http://localhost:8080/absproxy/3454 `
371
+
372
+ Read more about ` publicPath ` in the [ Vue.js docs] ( https://cli.vuejs.org/config/#publicpath )
You can’t perform that action at this time.
0 commit comments