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
System:
OS: Linux 3.10 CentOS Linux 7 (Core)
CPU: (16) x64 Intel(R) Xeon(R) CPU L5630 @ 2.13GHz
Binaries:
Node: 10.15.3 - /usr/bin/node
Yarn: 1.16.0 - ~/.yarn/bin/yarn
npm: 6.4.1 - /usr/bin/npm
Browsers:
Chrome: Not Found
Firefox: Not Found
npmGlobalPackages:
@vue/cli: Not Found
Steps to reproduce
Launch Vue UI on remote machine (vue ui --host 192.168.1.100), connect to UI, select a project and "serve" it. When compiled, the "open app" button will get enabled. Click on it and a new tab will open, but on localhost:8080 instead of 192.168.1.100:8080
What is expected?
I'd expect that the new tab would open on 192.168.1.100:8080 address
What is actually happening?
The new tab opens on localhost:8080 address
I understand that VueCLI is not made for remote work, but it would be very nice to have this issue sort of fixed. I am moving my whole "working" setup on one of my home servers and VueCLI is just too good to be left out.
The text was updated successfully, but these errors were encountered:
So when someone would be at localhost:8000/tasks/leProject:serve the new tab would open at localhost:8080
And when someone would have the UI on a remote machine (ex. 192.168.1.100:8000/leProject:serve) the new tab would open on http://192.168.1.100:8080
Version
3.7.0
Environment info
Steps to reproduce
Launch Vue UI on remote machine (
vue ui --host 192.168.1.100
), connect to UI, select a project and "serve" it. When compiled, the "open app" button will get enabled. Click on it and a new tab will open, but onlocalhost:8080
instead of192.168.1.100:8080
What is expected?
I'd expect that the new tab would open on
192.168.1.100:8080
addressWhat is actually happening?
The new tab opens on
localhost:8080
addressI understand that VueCLI is not made for remote work, but it would be very nice to have this issue sort of fixed. I am moving my whole "working" setup on one of my home servers and VueCLI is just too good to be left out.
The text was updated successfully, but these errors were encountered: