drukscode/drukscode-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
drukscode-v2/docs/guide/more-features/port-manager.md
OpenCode AI e9899d2e6d
Some checks failed
Android CI Build / check (push) Has been cancelled
Details
Android CI Build / package-apks (push) Has been cancelled
Details
Docs Deploy / build (push) Has been cancelled
Details
Module Market Check / Validate modules/ (push) Has been cancelled
Details
Module Market Publish / Generate submissions.json (push) Has been cancelled
Details
Docs Deploy / deploy (push) Has been cancelled
Details
Initial DruksCode V2: fresh fork of web-to-app (f3b488e) with DruksCode identity 
- Package rename com.webtoapp -> br.com.drukstech.codeapp
- Product rename WebToApp/web-to-app -> DruksCode/drukscode
- Design system Wta* -> Dkc*
- applicationId br.com.drukstech.codeapp (.play for gplay flavor)
- rootProject.name DruksCode
- Fresh git history (upstream kept as remote for sync)
2026-09-12 02:42:02 +02:00

1.0 KiB
Raw Permalink Blame History

Port Manager

Coordinates the local-server ports used by runtime apps across all your generated apps. Open it from ⋮ → Port Manager.

Features

  • Service list — see which ports are in use, the owning process, and latency.
  • Kill — stop a single service, or kill all.
  • Auto-refresh — keep the list current.
  • Port ranges — view the configured port ranges.
  • Copy port / open — quick actions per entry.
  • Filters — show all services or filter; detects DruksCode apps specifically.
  • Status — responding / not responding indicators.

Conflict policy

When a runtime needs a port that's taken, the configured policy applies:

  • AUTO_KILL — stop the conflicting service.
  • ALERT — notify and let you decide.

(REASSIGN — picking another port — is the engine's internal fallback for zero/unconfigured ports, not a user-selectable policy.)

Notes

Runtimes allocate through the Port Manager and release their port on stop, so ports don't leak between apps.