Re:Octant: A tool to help devs understand what's going on in...
by johnmarcus on Thursday August 08, 2019 @11:48AM
(#20645592)
why does it start up on a random port, which is different each time? and it's not configurable? that makes it a real pita to run in a docker container...which is kind of the environment.
[ Parent
| on HN ]
Re:Octant: A tool to help devs understand what's going on in...
by bryanl on Friday August 09, 2019 @03:00PM
(#20657340)
(i'm the author)
We had a choice to make. We could have used a port, but then would have had to find a solution for when that port was used. So the choice was made to use a random port.
Re:Octant: A tool to help devs understand what's going on in...
by johnmarcus on Monday August 12, 2019 @06:12AM
(#20674049)
i think you should re-consider this choice for a few reasons.
- every software has to do this, and they pretty much just do it and make it an option to configure.
- just assume folks will run this in a docker container and it becomes an entirely mute point.
- you have literally ostracized your core audience by making it impossible to run in a docker container.
just some thoughts. wish i could try it, but i'm not firing up my linux vm just to do so, knowing I can't run it reliably anywhere (because if it's choosing random ports, how will i now it won't randomly conflict with something?)
Re:Octant: A tool to help devs understand what's going on in...
by johnharris85 on Friday August 09, 2019 @02:28PM
(#20657075)
It is configurable:
`OCTANT_LISTENER_ADDR=127.0.0.1:8900 octant`
Re:Octant: A tool to help devs understand what's going on in...
by johnmarcus on Monday August 12, 2019 @09:15PM
(#20681905)
thanks! i made a pull request to add to the docs. it's a cool project once i got this running.