[Feature] Remote AnalysisSee original GitHub issue
Is your feature request related to a problem? Please describe.
Dbux’s Runtime Server is currently hard-coded to live on port
@dbux/runtime connects to
localhost:3374. Thus, remote applications cannot currently be debugged.
Describe the solution you’d like
This should be configurable in order to allow debugging remotely executed code as well as containers.
Is this covered by any of the Dbux known limitations or future-work items? If so, which?
Please let us know on discord and up-vote this feature, if this issue is blocking you from using Dbux.
- Created 2 years ago
- Comments:14 (14 by maintainers)
Top GitHub Comments
…OK I realized, the port forwarding “works” only to the extent that it successfully loads the trace into dbux in VSCode.
But then it obviously fails to do anything useful with it because the file doesn’t exist locally.
So I guess the only working way (which luckily is also the most straight forward one) is to use the remote SSH extension for VSCode and simply use dbux in the remote VSCode session.
Will probably look into Volta indeed, because I’m currently using asdf and it annoys the heck out of me.