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

Document how to make the server portable #53

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

annismckenzie
Copy link

As mentioned in #50 (comment) I wanted to document the findings on how to make the server portable and allow it to be moved to a different machine.

I took the liberty of renaming id to ID in the document because its all-uppercase version is generally accepted and encouraged (see https://google.github.io/styleguide/go/decisions#initialisms and https://go.dev/talks/2014/names.slide#5) but I can also undo that change.

Thanks for an awesome library!

This takes a couple bits from the preceding part but puts it into a list
to allow for easier readability.
computer (like a new Raspberry Pi), a certain number of requirements and steps are necessary:

1. The bridge has the ID `1`.
2. All of your accessories have unique IDs that don't change. This is important: `hap` automatically assigns the IDs for you
Copy link
Author

Choose a reason for hiding this comment

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

Suggested change
2. All of your accessories have unique IDs that don't change. This is important: `hap` automatically assigns the IDs for you
2. All of your accessories have unique IDs that don't change.\
**This is important:** `hap` automatically assigns the IDs for you

This would probably read better.

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.

1 participant