Resolving Port Conflicts When Manually Starting Phoenix Server

I can start a server manually with ` py -m phoenix.server.main serve` , but then the script doesn't run, because the port numbers conflict

· Sorted by Oldest

Roger Y.
·
you can comment out this line in the script after starting the server manually
session = px.launch_app()
Roger Y.
·
comment out this line also because the server is now external to the script
px.active_session().url
Thomas A.
·
But then I'm not using px at all
Thomas A.
·
So how does it know to contact the server?
Thomas A.
·
Is it enough to simply import phoenix?
Roger Y.
·
there’s a default url that all components share beforehand so they’ll contact the server at the same location
Roger Y.
·
if you need something non-default, say a different port, then they can be set via environment variables such as PHOENIX_PORT or `PHOENIX_COLLECTOR_ENDPOINT`
Roger Y.
·
another example is if the server is remote, then you would specify the URL via PHOENIX_COLLECTOR_ENDPOINT
Thomas A.
·
Thank you!
Roger Y.
·
np

Roger Y.
·
you can comment out this line in the script after starting the server manually
session = px.launch_app()
Roger Y.
·
comment out this line also because the server is now external to the script
px.active_session().url
Thomas A.
·
But then I'm not using px at all
Thomas A.
·
So how does it know to contact the server?
Thomas A.
·
Is it enough to simply import phoenix?
Roger Y.
·
there’s a default url that all components share beforehand so they’ll contact the server at the same location
Roger Y.
·
if you need something non-default, say a different port, then they can be set via environment variables such as PHOENIX_PORT or `PHOENIX_COLLECTOR_ENDPOINT`
Roger Y.
·
another example is if the server is remote, then you would specify the URL via PHOENIX_COLLECTOR_ENDPOINT
Thomas A.
·
Thank you!
Roger Y.
·
np