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

Liberty Bikes Conference Demo Setup Instructions #181

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hlhoots
Copy link
Member

@hlhoots hlhoots commented Apr 18, 2019

No description provided.

# Hardware needed:

1. Laptop with Liberty Bikes code
2. Ethernet cable
Copy link
Contributor

Choose a reason for hiding this comment

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

This is optional right? I assume it's for giving a direct connection between the host laptop and the router?

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 just personally like having a hardwire vs a wifi connection from a reliability / performance standpoint. It also allows for the wired NIC to be used for the game, and your wireless NIC can also connect to the conference wifi so you can show webpages like openliberty.io, liberty bikes github, etc.

Copy link
Contributor

Choose a reason for hiding this comment

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

agreed that it's nice to have, but we should still list it as optional, so people don't think it's a requirement to run the demo

4. Up to 4 mobile devices (one for each player)


# Router setup (linksys)
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think most people running this at a conf would be able to follow these steps -- it seems like pretty advanced stuff. When I did this at EclipseCon, we didn't have to mess around with network config at all really. We just connected everything up to the wifi network and used hardcoded IP addresses. Maybe instead we can explain how to check the frontend service's logs to determine what IP the endpoint is available at?

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 will play around next week with a setup similar to yours and see if I can simplify.

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.

2 participants