RealDevSquad / RealDevSquad/website-backend
[RFC] To run our server on some other port instead of 80
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Port 80 requires superuser permissions to be used.
Running npm packages with sudo privileges is scary, as npm can run shell scripts also.
Instead, we could NAT port 80 to say port 3000, so that our app will be available on both ports.
This way we would not have to run our local dev server on port 80, and CORS would not arise.
Only the hosted server would have to make those changes, and we could slowly migrate our APIs to talk to our secret port instead.
Reference to create changes on server.
Reference to avoid using sudo npm on local machine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points, so first locate how the Node.js server binds port 80 and how the hosted deployment is configured. Review the two linked references and resolve the proposed NAT or alternate-port approach; done means the server is available on both ports without requiring sudo for local npm usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100