2020-11-12 13:30:52 +00:00
|
|
|
# TUNNEL_RELAY_URL
|
|
|
|
|
# The URL of the Telebit Relay, of course.
|
|
|
|
|
# Note that many client configuration details can be preassigned at
|
|
|
|
|
# https://devices.example.com/.well-known/telebit.app/index.json
|
2020-07-22 08:05:30 +00:00
|
|
|
TUNNEL_RELAY_URL=https://devices.example.com/
|
2020-11-12 13:30:52 +00:00
|
|
|
|
|
|
|
|
# VENDOR_ID
|
|
|
|
|
# Used to distinguish between different white-labeled Telebit binaries.
|
|
|
|
|
# It's just as well to generate a random ID for your organization.
|
|
|
|
|
VENDOR_ID=
|
|
|
|
|
|
|
|
|
|
# Used for Let's Encrypt registration
|
|
|
|
|
# ACME_AGREE
|
|
|
|
|
ACME_AGREE=true
|
|
|
|
|
# ACME_EMAIL
|
|
|
|
|
ACME_EMAIL=johndoe@example.com
|
|
|
|
|
|
|
|
|
|
# CLIENT_SUBJECT (optional)
|
|
|
|
|
# NOT used by Telebit.
|
|
|
|
|
# This is for the Device Management & Authentication server.
|
|
|
|
|
CLIENT_SUBJECT=newbie
|
2020-06-29 08:56:48 +00:00
|
|
|
CLIENT_SECRET=xxxxxxxxxxxxxxxx
|
2020-07-22 08:05:30 +00:00
|
|
|
LOCALS=https:$CLIENT_SUBJECT.devices.example.com:3000,https:*.$CLIENT_SUBJECT.devices.example.com:3000
|
2020-11-05 09:11:17 +00:00
|
|
|
#ACME_HTTP_01_RELAY_URL=http://localhost:4200/api/http
|
2020-07-18 05:28:12 +00:00
|
|
|
#PORT_FORWARDS=3443:3001,8443:3002
|
|
|
|
|
#DUCKDNS_TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
|
2020-11-12 13:30:52 +00:00
|
|
|
|
|
|
|
|
# AUTH_URL
|
|
|
|
|
# The client may receive this as `.authn.url`
|
|
|
|
|
# through `https://$API_DOMAIN/.well-known/telebit.app/index.json`
|
|
|
|
|
# Setting the ENV AUTH_URL or the flag --auth-url overrides the discovery endpoint
|
