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

Port 3030 in use #102

Closed
nsantini opened this Issue Oct 26, 2016 · 3 comments

Comments

4 participants
@nsantini

nsantini commented Oct 26, 2016

Looks like the next server is clashing with another service I have running on 3030. Whats the full list of ports needed to run next in production and how can they be changed?

@nkzawa

This comment has been minimized.

Show comment
Hide comment
@nkzawa

nkzawa Oct 27, 2016

Member

3030 is used to run webpack-dev-server only on development.
We'd like to support customizing the port number.

For production, there is no fixed port to be used.
You can change it when starting your app like:

next build
next start -p 8080

For development:

next -p 8080
Member

nkzawa commented Oct 27, 2016

3030 is used to run webpack-dev-server only on development.
We'd like to support customizing the port number.

For production, there is no fixed port to be used.
You can change it when starting your app like:

next build
next start -p 8080

For development:

next -p 8080
@jayres

This comment has been minimized.

Show comment
Hide comment
@jayres

jayres Oct 27, 2016

Moreso, if you want to always load from that specific port without typing it in every time you can specify that in the startup script in your package.json.

"scripts": { "dev": "next -p 8080" },

jayres commented Oct 27, 2016

Moreso, if you want to always load from that specific port without typing it in every time you can specify that in the startup script in your package.json.

"scripts": { "dev": "next -p 8080" },

@thisguychris

This comment has been minimized.

Show comment
Hide comment
@thisguychris

thisguychris Oct 30, 2016

Contributor

@nkzawa is there any plan to add the cli options for next in the README.md ?

Contributor

thisguychris commented Oct 30, 2016

@nkzawa is there any plan to add the cli options for next in the README.md ?

@nkzawa nkzawa closed this Dec 2, 2016

@lock lock bot locked as resolved and limited conversation to collaborators May 12, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.