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

Improve README with instructions on installing bun and the backend providers #588

Merged
merged 3 commits into from
Nov 24, 2023

Conversation

rafaellehmkuhl
Copy link
Member

@rafaellehmkuhl rafaellehmkuhl commented Nov 23, 2023

It was reported by @DonLakeFlyer that bun, when installed from Snap, has not been able to install the repository libraries.

@rafaellehmkuhl rafaellehmkuhl changed the title Add suggestion in the README to install bun following their docs Improve README with instructions on installing bun and the backend providers Nov 23, 2023
README.md Outdated

If you're serving `mavlink2rest` in the same machine as Cockpit, activate the checkmark for "Mavlink2Rest connection" and use `ws://0.0.0.0:8088/v1/ws/mavlink` there (if you're running a mavlink2rest version before 0.11.15, omit the `/v1` in the URL).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you're serving `mavlink2rest` in the same machine as Cockpit, activate the checkmark for "Mavlink2Rest connection" and use `ws://0.0.0.0:8088/v1/ws/mavlink` there (if you're running a mavlink2rest version before 0.11.15, omit the `/v1` in the URL).
If you're serving `mavlink2rest` in the same machine as Cockpit, activate the checkmark for "Mavlink2Rest connection" and use `ws://127.0.0.1:8088/v1/ws/mavlink` there (if you're running a mavlink2rest version before 0.11.15, omit the `/v1` in the URL).

README.md Outdated

If you're serving `mavlink-camera-manager` in the same machine as Cockpit, activate the checkmark for "WebRTC connection" and use `ws://0.0.0.0:6020` there.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you're serving `mavlink-camera-manager` in the same machine as Cockpit, activate the checkmark for "WebRTC connection" and use `ws://0.0.0.0:6020` there.
If you're serving `mavlink-camera-manager` in the same machine as Cockpit, activate the checkmark for "WebRTC connection" and use `ws://127.0.0.1:6020` there.

Copy link
Member Author

@rafaellehmkuhl rafaellehmkuhl Nov 23, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it worked for Don using 0.0.0.0. Have you tested with 127.0.0.1? If so I will change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it works, but it doesn't mean it is right. if they are on the same machine, 127.0.0.1 will work.

Copy link
Member Author

@rafaellehmkuhl rafaellehmkuhl Nov 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes yes, you're right. 0.0.0.0 usually just means "anyone" for server side. I'm just afraid for no reason haha
Will change.

Copy link
Member Author

@rafaellehmkuhl rafaellehmkuhl Nov 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Solved.

Copy link
Contributor

@ES-Alexander ES-Alexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Language looks ok to me :-)

I haven't tried the actual instructions, so not sure if there are any issues with the steps.

Copy link
Member

@Williangalvani Williangalvani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice =]

README.md Outdated
2. Run the MAVLink router, connecting it to your vehicle or [SITL instance](https://ardupilot.org/dev/docs/sitl-simulator-software-in-the-loop.html).
3. Install [mavlink2rest](https://github.com/mavlink/mavlink2rest).
4. Run `mavlink2rest`, pointing it to the endpoint provided by the MAVLink router. Remember to serve the API over the 6040 port by running it with `--server 127.0.0.1:6040`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont mind servers at 0.0.0.0, as that means "bind to all interfaces available". Just connecting to 0.0.0.0 as a client that is conceptually... dubious

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed that one by mistake 🤦
That's exactly the case for 0.0.0.0 haha
Fixing before merging.
Good catch.

@rafaellehmkuhl rafaellehmkuhl merged commit 406da25 into bluerobotics:master Nov 24, 2023
7 checks passed
@rafaellehmkuhl rafaellehmkuhl deleted the improve-readme branch November 24, 2023 02:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants