4 ms·

What web framework commonly uses 5000 in development mode? I've seen a lot of port 3000 and 8888 and 8080 and 10000, but never 5000.

Kwpolska 5y ago
Flask is one example: https://flask.palletsprojects.com/en/2.0.x/quickstart/#a-minimal-application https://flask.palletsprojects.com/en/2.0.x/quickstart/#a-min...
detaro 5y ago
Flask, svelte.js' "sirv", angulars "ng serve", ASP.NET
- Shacklz 5y ago
  Angulars "ng serve" defaults to 4200 as far as I'm aware; never seen 5000 in the wild in the context of Angular
deleted 5y ago
[deleted]
bryanrasmussen 5y ago
we ran into it recently, basically when running microservices locally the different services were running on different ports, obviously don't need all running but there was a collision. The main problem is that with Apple's normally great communication skills about what they do, it takes a while to figure out what has all of a sudden happened and then change your port. And then you're mad at apple for making you waste some time.
- op00to 5y ago
  Looking at open ports takes a while?
  - bryanrasmussen 5y ago
    one of the things I often hear is that people don't like to go repeat the same action a bunch of times, so for example if one has a bunch of microservices meant to be run through docker one does not want to go set ports up for all scenarios etc. and to have every member of a team do the same thing, and maybe updating documentation because you've written in port 5000 all over the place, hah hah, but no to answer your no doubt sincere question looking up open ports does not take a while. What takes a while is another engineering principle that people are sometimes bitten by, trying to understand why a change in the system has occurred - in this case why your port that you always use is suddenly no longer open despite you not having done anything that you are aware of that might have closed it. Of course you want to understand why this change has happened because it seems weird, is there something nefarious going on at port 5000 now!?! Also because of all the things said above about wanting to not change all occurrences of 5000 in your developer docs and so forth so it would be nice if you figure out, as was shown as the top voted answer of the article, that you could go to somewhere in settings and turn off this usage of the port. I mean you could just scan and change what port you use to another currently open port without worrying about any of this stuff, which I guess would have worked in this case but I can't help but feel that would not really appear the best move whenever strange unexplained port usage changes occur. Your mileage evidently varies.
ojhughes 5y ago
Not a web framework but running a local docker registry uses port 5000 by default

Kwpolska 5y ago

Flask is one example: https://flask.palletsprojects.com/en/2.0.x/quickstart/#a-minimal-application https://flask.palletsprojects.com/en/2.0.x/quickstart/#a-min...

detaro 5y ago

Flask, svelte.js' "sirv", angulars "ng serve", ASP.NET

Shacklz 5y ago
Angulars "ng serve" defaults to 4200 as far as I'm aware; never seen 5000 in the wild in the context of Angular

deleted 5y ago

[deleted]

bryanrasmussen 5y ago

we ran into it recently, basically when running microservices locally the different services were running on different ports, obviously don't need all running but there was a collision. The main problem is that with Apple's normally great communication skills about what they do, it takes a while to figure out what has all of a sudden happened and then change your port. And then you're mad at apple for making you waste some time.

op00to 5y ago
Looking at open ports takes a while?
- bryanrasmussen 5y ago
  one of the things I often hear is that people don't like to go repeat the same action a bunch of times, so for example if one has a bunch of microservices meant to be run through docker one does not want to go set ports up for all scenarios etc. and to have every member of a team do the same thing, and maybe updating documentation because you've written in port 5000 all over the place, hah hah, but no to answer your no doubt sincere question looking up open ports does not take a while. What takes a while is another engineering principle that people are sometimes bitten by, trying to understand why a change in the system has occurred - in this case why your port that you always use is suddenly no longer open despite you not having done anything that you are aware of that might have closed it. Of course you want to understand why this change has happened because it seems weird, is there something nefarious going on at port 5000 now!?! Also because of all the things said above about wanting to not change all occurrences of 5000 in your developer docs and so forth so it would be nice if you figure out, as was shown as the top voted answer of the article, that you could go to somewhere in settings and turn off this usage of the port. I mean you could just scan and change what port you use to another currently open port without worrying about any of this stuff, which I guess would have worked in this case but I can't help but feel that would not really appear the best move whenever strange unexplained port usage changes occur. Your mileage evidently varies.

ojhughes 5y ago

Not a web framework but running a local docker registry uses port 5000 by default