Skip to content
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

Multiple RW apps all use the same debug port #10937

Open
1 task
Tobbe opened this issue Jul 11, 2024 · 2 comments
Open
1 task

Multiple RW apps all use the same debug port #10937

Tobbe opened this issue Jul 11, 2024 · 2 comments

Comments

@Tobbe
Copy link
Member

Tobbe commented Jul 11, 2024

What's not working?

If you just try to simultaneously run two RW apps the second one won't start because the 8910 and 8911 ports are already taken.
So you go and update your redwood.toml file to run your second app on 8912 and 8913.
Now everything starts up just fine 🎉

The problem though is that they both launch with --debug-port 18911. That port should probably default to '1' + ${apiPort} to reduce the risk of conflicting ports.

I noticed this when running ps aux | grep rw-

First app, api side running on :8911
image

Second app, api side running on :8913
image

Notice how they both have the same debug port

How do we reproduce the bug?

See above. Run two RW apps at the same time.

Are you interested in working on this?

  • I'm interested in working on this
@Tobbe Tobbe added bug/needs-info More information is needed for reproduction good first issue topic/cli and removed bug/needs-info More information is needed for reproduction labels Jul 11, 2024
@gracemorganmaxwell
Copy link

I am keen to assist @Tobbe; I know exactly what you mean; I've experienced this behaviour before, when running two instances at the same time, usually because I forgot about the first one still be active.

I'm guessing the place to start a part from replicating the issue, is to find the file that controls that logic for the debug port and testing your theory out of 1 + ${apiport}.

@callingmedic911
Copy link
Member

First off, thanks for offering your help here @gracemorganmaxwell!

@Tobbe cmiiw, but similar to apiPort you can change debugPort in redwood.toml to a different value. However, we could have random port logic if there's no value set for any of the ports (api, debugger, others?). Though it would be a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants