filex-signal - the filex rendezvous (signaling) relay (Windows)
===============================================================

Run your own relay so transfers don't depend on anyone else's. It only brokers
the WebRTC handshake -- file bytes go directly peer-to-peer and never pass
through this server, so its bandwidth stays tiny no matter the file size.

QUICK START
  filex-signal.exe              reads filex-signal.json next to it (a commented
                                default is written on the first run)
  filex-signal.exe 8080         quick mode: just listen on port 8080
  filex-signal.exe my.json      use a specific config file

CONFIG (filex-signal.json)
  Edit it to set the port, an optional password, resource limits, TLS, and
  allow_turn (set false to forbid TURN-relayed transfers entirely). The
  FILEX_SIGNAL_PASSWORD environment variable overrides the password.

EXPOSING IT
  Open the chosen port in your firewall / router and point clients at
  ws://your-host:<port>. For a public server, prefer wss:// (enable TLS in the
  config, or terminate TLS at a reverse proxy) so the password and codes
  aren't sent in cleartext.

  Keep filex-signal.exe together with the .dll files in this folder.

Source & docs: https://github.com/Remotesh/fileTransfer
License: MIT (see LICENSE.txt). Bundled libraries keep their own licenses
(libdatachannel MPL-2.0, OpenSSL Apache-2.0).
