Dcntrlized/alarm-client
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[chore](client): point the dev tasks at the instance origin

Browse Source 
The adb reverse and launch tasks now forward the instance port (8080) instead of the retired direct service port, matching the single-origin transport.
This commit is contained in:
Admin
2026-10-19 02:34:20 +01:00
parent d70d708230
commit ac366b8333
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.vscode/tasks.json
Vendored
+5 -6
View File
@@ -1,12 +1,11 @@
{
// Alarm client (bare React Native, no Expo) — house task set.
// Metro is pinned to 127.0.0.1:8089 (see android/gradle.properties and
// package.json's `start` script). 8088 is NOT Metro here: it is the Alarm
// service's documented host port, so direct mode reverses it separately and
// the two can never fight over one host port.
// package.json's `start` script). The app talks to ONE origin, the instance
// on 8080 — every service is a path under it, so the service's own 8088 is
// never reversed and nodes never need a second tunnel.
// device 127.0.0.1:8089 -> host 127.0.0.1:8089 (Metro packager)
// device 127.0.0.1:8088 -> host 127.0.0.1:8088 (Alarm direct)
// device 127.0.0.1:8080 -> host 127.0.0.1:8080 (Maestro)
// device 127.0.0.1:8080 -> host 127.0.0.1:8080 (instance/Maestro origin)
"version": "2.0.0",
"tasks": [
{
@@ -36,7 +35,7 @@
{
"label": "Setup adb reverse",
"type": "shell",
"command": "adb reverse tcp:8089 tcp:8089 && adb reverse tcp:8088 tcp:8088 && adb reverse tcp:8080 tcp:8080 && adb reverse --list",
"command": "adb reverse tcp:8089 tcp:8089 && adb reverse tcp:8080 tcp:8080 && adb reverse --list",
"problemMatcher": []
},
{