Inyon0.17.5

Reference

Configuration

Every setting for a hub and for inyon, the files they live in, and the ports Inyon uses.

Most people never set anything by hand: inyon setup writes what it needs. This page lists everything you can set.

Hub settings

An installed hub reads ~/.inyon/hub.env, one NAME=value per line, and inyon setup writes it for you. Variables set in the environment win over the file. A hub run from source reads only the environment.

VariableDefaultWhat it does
PORT4777The port to listen on
BIND127.0.0.1The address to listen on. Anything but localhost needs TLS_CERT and TLS_KEY, or INYON_ALLOW_HTTP=1; otherwise the hub refuses to start
INYON_ALLOW_HTTP1 serves plain http on a network address, for a VPN that encrypts on its own
TLS_CERT, TLS_KEYPEM certificate and key files, to serve HTTPS directly
INYON_ALLOWED_HOSTSExtra host names the hub answers to, comma-separated. IPs, single-label names, localhost, .ts.net, NetBird names and home-network names (.local, .lan, .internal, .home.arpa) always work. * turns the check off
INYON_ALLOWED_ORIGINSExtra origins allowed to call the hub, comma-separated, for a reverse proxy on another hostname
INYON_DATA_DIR~/.inyonWhere the hub keeps its records
INYON_HUB_NAMEthe machine's nameThe name phones show for this hub
INYON_DOWNLOADthis version's releaseWhere the hub fetches the files it hands to joining machines

The host check guards against DNS rebinding: a web page on another site can't reach the hub by pointing a name at its address.

Computer settings

These are read by inyon and inyon-engine on any computer.

VariableWhat it does
INYON_TOKENThe machine's token when joining a hub
INYON_HUBThe hub to connect to (saved by join)
INYON_DOWNLOADWhere to fetch releases from, instead of this site's copy of the newest one (https://inyon.abhashchakraborty.tech/download)
INYON_ENGINEUse this inyon-engine instead of the installed one
INYON_NO_MODIFY_PATHSet to 1 before running get.sh or get.ps1 to keep them from putting inyon on your PATH (from 0.17.1). See Put inyon on your PATH
INYON_WEB_URLThe page pairing QR codes open, for your own browser copy
INYON_ALLOW_INSECUREAllow sending the machine's token to a hub over plain http on a public address. Don't
NO_COLORTurn colour off in the terminal

Every TETHER_* name from before the rename is still read as its INYON_* twin.

A paired computer's link options are saved in ~/.inyon/node/link.json whenever you pass them to inyon pair or choose them in inyon setup. See Pairing a computer.

App settings

Display settings (theme, reply font, haptics…) are saved per device. Upload limits and session restarts are saved on the hub, or in the app for its own computers. Settings lists them all.

Files

PathWhat's there
~/.inyon/bin/inyon, inyon-engine, cloudflared
~/.inyon/node/A computer's key, paired phones, link options, hub connection, logs, update status
~/.inyon/hub.envAn installed hub's settings
~/.inyon/A hub's records: password hash, machines, phones, settings, drafts, saved chats, offline snapshots
~/.inyon/uploads/Files you attached, per day and session
~/.inyon/upload-policyFrom 0.17, the upload rules the hub last used on this machine, so it can tidy by itself
~/.inyon/setup-codeA new hub's setup code, until the password is set

Folders are readable only by you, and the files with keys or tokens only by you.

Ports

PortWhat listensWhere
4777A hub127.0.0.1 unless you choose a network
4780A paired computer's link127.0.0.1, plus each private network's address, plus every interface with LAN on

A computer that joined a hub listens on nothing: it connects out. The Android app listens on nothing either.

Edit this page on GitHub