-
Notifications
You must be signed in to change notification settings - Fork 12k
ng serve --deploy-url / --base-url / --public-host
doesn't affect live-reload paths
#6932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please see PR #6320 This should be available in the next minor release. |
Thanks |
The linked PR appears stale - re-opening issue. |
Fixed via #6320 (it's merged now). |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report or Feature Request (mark with an
x
)Versions.
macOS 10.12.5
Repro steps.
When running
ng serve
inside a subdirectory (--deploy-url /app1/ --base-url /app1/
) the live reload setup is still served from the root url.When developing two angular apps on the same host/port (behind a reverse proxy for example), this is problematic.
I thought setting
--public-host http://mydevserver/app1/
would help, but it does not seem to affect live reload.The log given by the failure.
Console errors:
zone.js:2263 GET http://devserver/app1/info?t=1499685597179 404 (Not Found)
Desired functionality.
Setting
--public-host
should also set up live-reload to operate from the same URL.Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: