GlinkBot documentation

Server deployment

GlinkBot server availability and remote-access boundaries.

Current distribution

GlinkBot is distributed as application builds. The desktop bundles the server, web interface, and phone companion. A separately published npm package or container image is not required and is not currently offered as a GlinkBot installation path.

Use official download availability and the installation guide. Do not install an upstream package or container and assume it is GlinkBot.

Access from another device

Use the desktop connection controls to pair Android. A phone's localhost address does not refer to your desktop. The host must be running and reachable.

The server trusts loopback. Never expose its local port directly to the public internet. Remote access needs an authenticated and encrypted connection. A domain name alone does not provision a tunnel, authentication service, certificate, or server.

Operator-managed hosting

Private source deployments require an authorized checkout, an explicitly configured remote-access path, and an operator who maintains backups, engine credentials, TLS, and access controls. Managed accounts and tunnels are not promised merely because the source contains integrations.

There is no public GlinkBot VPS installer or registry command to copy here. Provider engines may require their own installation and sign-in on the host.

Data and recovery

Back up the selected data directory and protect secrets in configuration files. New workspaces default to ~/.glinkbot. Do not overwrite a live workspace during a migration or assume a backup contains provider credentials held elsewhere.

GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.