Install doc doesn't mention the port the server listens on
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript, node.js
- Domain
- documentation, networking
Research direction
Start with the install guide’s server-start section, then verify the defaults in daveappserver and config.json. Update the documentation to state the HTTP port 1420 or PORT value and the WebSocket port 1462 or websocketPort value, including the reverse-proxy requirement.
Written by the indexing model from the issue text.
Description
Doing a test install using Claude Code, I noticed it took a long time for it to find the proper port to be proxied. Here is Claude's suggestion.
The install guide tells you to start the server with node rssnetwork.js and to set up a reverse proxy, but it never says what port to point that proxy at.
The answer is buried in daveappserver: the default is process.env.PORT || 1420, discoverable only by downloading the package and reading its source. Anyone following the guide who wants to put Caddy or nginx in front of the app has to go hunting for it.
A one-line addition to the install doc would fix this — either in the "Start the server" step or in a dedicated networking/ports section:
▎ The server listens on port 1420 by default (or the value of the PORT environment variable). Point your reverse proxy at that port.
It would also be worth mentioning the WebSocket port (1462 by default, set via websocketPort in config.json), since anyone running behind a reverse proxy needs to forward WebSocket upgrade requests to it separately.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from scripting/rss.chat
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in scripting/rss.chat
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
automated broken-link
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·