You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For someone using BlueOS, it's easy to connect to the vehicle as no additional tools are required, but for those without BlueOS, that are running all the backend providers in their own machine, there are a lot of steps to get up and running.
It would be really good for the project if we could have a Docker image with all the necessary tools (mavlink-router/mavp2p, mavlink2rest and mavlink-camera-manager) included.
A nice bonus would be if it had a SITL instance already connected, for those without a flight-controller.
Solving this issue would really help the project, as it's the main entrance barrier today for someone that wants to start contributing to Cockpit.
The text was updated successfully, but these errors were encountered:
For someone using BlueOS, it's easy to connect to the vehicle as no additional tools are required, but for those without BlueOS, that are running all the backend providers in their own machine, there are a lot of steps to get up and running.
It would be really good for the project if we could have a Docker image with all the necessary tools (mavlink-router/mavp2p, mavlink2rest and mavlink-camera-manager) included.
A nice bonus would be if it had a SITL instance already connected, for those without a flight-controller.
Solving this issue would really help the project, as it's the main entrance barrier today for someone that wants to start contributing to Cockpit.
The text was updated successfully, but these errors were encountered: