Files
AndroidDeviceStreaming/deploy/README.md
T

1.6 KiB

Process management examples

Actual multi-node deployment is documented in docs/cluster.md. Earlier single-node deployment and startup commands are in docs/deployment-ttstd.md.

Examples are templates, not installed automatically. Replace paths, domain, user and tokens before use. Public endpoints require HTTPS/WSS.

  • Linux: create a dedicated ads user and /opt/ads; protect /etc/ads/*.env so only the intended account/root can read them. server.env contains ADS_AGENT_TOKEN=... and ADS_CLIENT_TOKEN=...; agent.env contains only ADS_AGENT_TOKEN=.... Copy the respective systemd unit to /etc/systemd/system/, then enable it. The local client normally runs as the desktop user, so it shares that user's ADB server and keys.
  • macOS: edit the launchd plist, restrict its file permissions, and install it as the appropriate user's LaunchAgent. It contains a credential, so do not publish the edited file. Client launchd configuration can use the same pattern with ads-client and ADS_CLIENT_TOKEN.
  • Windows: the gateway can be hosted as a background Scheduled Task using deploy/windows/; installation and task restart have been verified on the remote Windows PC. Credentials stay in an ACL-protected directory and the account password is stored by Task Scheduler. Native Service Control Manager support is not implemented; do not use sc.exe create directly on these binaries.

The Linux server unit has been deployed and verified on Debian 12. Agent service and macOS templates still require target-platform validation.