-
Notifications
You must be signed in to change notification settings - Fork 3
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 development setup docs #1807
Conversation
The command has to be run every time a device is connected. | ||
|
||
```shell | ||
adb reverse tcp:8081 tcp:8081 && adb reverse tcp:8000 tcp:8000 && adb reverse tcp:5002 tcp:5002 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This includes port forwarding for integreat as I figured having one command in the history for this makes sense. However, I am also open to keep it entitlementcard only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm we have the expose:ports
that can be triggered via npm run expose:ports
i think you should even update this (it also checks for attached devices) and add the command here
9bd2ca6
to
1f2db62
Compare
@@ -1,4 +1,3 @@ | |||
version: "3.5" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is obsolete and led to a warning on startup.
See https://docs.docker.com/reference/compose-file/version-and-name/.
1f2db62
to
e19ff17
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
The command has to be run every time a device is connected. | ||
|
||
```shell | ||
adb reverse tcp:8081 tcp:8081 && adb reverse tcp:8000 tcp:8000 && adb reverse tcp:5002 tcp:5002 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm we have the expose:ports
that can be triggered via npm run expose:ports
i think you should even update this (it also checks for attached devices) and add the command here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks nice 👍
Short description
I cleaned up the development setup with new best practices.
Proposed changes
Side effects
Testing
None.
Resolved issues
Fixes: None.