Configuration

Keep your connections together in a readable config file.

One file, several tunnels

WireRift accepts YAML and JSON. Describe your server connection once, then define the local services to expose. Keep a file containing a real token outside source control.

# wirerift.yaml
server: tunnel.example.com:4443
token: YOUR_TOKEN

tunnels:
  - type: http
    local_port: 3000
    subdomain: myapp
    inspect: true

  - type: tcp
    local_port: 5432

Start from the file

Pass the file explicitly. The config init command can generate a starting example.

wirerift config init
wirerift start wirerift.yaml
# JSON is also supported
wirerift start wirerift.json

Keep a token in the environment

The --token flag takes precedence over WIRERIFT_TOKEN. The server can generate a token when one is not supplied; use its startup output to configure your client.

export WIRERIFT_TOKEN=YOUR_TOKEN
wirerift http 3000 --server tunnel.example.com:4443

Set response headers per tunnel

HTTP tunnel options include inspection, access controls and custom response headers. Add them to individual entries instead of applying the same settings to every local service.

tunnels:
  - type: http
    local_port: 3000
    subdomain: preview
    auth: "reviewer:YOUR_PASSWORD"
    inspect: true
    headers: "X-Robots-Tag:noindex,X-Frame-Options:DENY"