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
I have a full API and I run it locally like so symfony server:start and yarn dev-server however, it seems that by default both run on port 8000. which introduces conflicts when it comes to routing.
If possible, how can I change the port for the encore server?
I attempted to run yarn dev-server --port 8080 but it seems that it still ran on 8000.
The text was updated successfully, but these errors were encountered:
Kerrialn
changed the title
How to define a different port?
How to define a different port for encore webpack?
Dec 13, 2021
just as an update I managed to run the apps on two separate ports by running encore dev-server --port 8080
the output doesn't look right to me:
➜ app:(master) ✗ encore dev-server --port 8080
Running webpack-dev-server ...
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:8080/, http://127.0.0.1:8080/
<i> [webpack-dev-server] Content not from webpack is served from '/.../public' directory
<i> [webpack-dev-server] 404s will fallback to '/index.html'
However, when I check http://localhost:8080/ I get 404 not found error.
I'm assuming this is because the Vue app on port 8080 isn't configured correctly to serve the correct files. as stated in the dev-server output "Content not from webpack is served".
How can I resolve this?
Kerrialn
changed the title
How to define a different port for encore webpack?
Content not from webpack is served
Dec 29, 2021
Stack:
I have a full API and I run it locally like so
symfony server:start
andyarn dev-server
however, it seems that by default both run on port 8000. which introduces conflicts when it comes to routing.If possible, how can I change the port for the encore server?
I attempted to run
yarn dev-server --port 8080
but it seems that it still ran on 8000.The text was updated successfully, but these errors were encountered: