-
Notifications
You must be signed in to change notification settings - Fork 377
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
Allow setting of the port number when using the --serve flag #1555
Labels
good first issue
Good for newcomers
Comments
15 tasks
I would like to take this issue. |
Riddhimaan-Senapati
added a commit
to Riddhimaan-Senapati/osv-scanner
that referenced
this issue
Jan 31, 2025
1.Added a global variable servePort with a default value of "8000" 2.Added a new CLI flag --port that allows users to customize the port number used when serving the HTML report 3. Removed the hardcoded port number from the ServeHTML function, using the global servePort variable instead 4. The flag's Action function updates the global servePort variable when a custom port is specified These changes allow users to specify a custom port using the --port flag when using the --serve option, while maintaining the default port 8000 if no custom port is specified.
Riddhimaan-Senapati
added a commit
to Riddhimaan-Senapati/osv-scanner
that referenced
this issue
Jan 31, 2025
…xed_issue_#1555 fixed issue google#1555
created a PR for this. |
Thanks for contributing! I've assigned tasks to you and will be reviewing your PRs. |
resolved in #1557 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The port is currently hardcoded to 8000:
osv-scanner/cmd/osv-scanner/internal/helper/helper.go
Line 132 in a5d0e2b
The text was updated successfully, but these errors were encountered: