tnl

module
v0.1.0-rc.42 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Nov 11, 2026 License: BSD-3-Clause

README

tnl

easy tunnels for dev and prod
by @0xcadams

tnl is not ready yet - first release is coming November 23.


tnl helps you connect to local and/or private services through end-to-end encrypted tunnels. It's like if Tailscale and Cloudflare Tunnel had a baby. And that baby came with a great devex.

tnl where?

in dev

tnl gives every Git worktree its own unique HTTPS URL. Traffic stays encrypted from the browser to your laptop.

For example, take a repo named demo with an app service. The main checkout and a perf worktree each get their own URL:

                             your browser
                                   |
                         https://*.example.com
                      (tnl.dev or your subdomain)
                                   v
                              tnl ingress
                         (hosted/self-hosted)
                                   |
                +------------------+------------------+
                |                                     |
           direct UDP                             tnl relay
        (when possible)                           (fallback)
                |                                     |
                +------------------+------------------+
                                   |
+----------------------------------v----------------------------------+
|                             your laptop                             |
|                                  |                                  |
|                +-----------------+----------------+                 |
|                v                                  v                 |
|       tnl (main checkout)                tnl (perf worktree)        |
|       app-demo.example.com            app-demo-perf.example.com     |
|                |                                  |                 |
|                v                                  v                 |
|         localhost:5173                     localhost:5174           |
+---------------------------------------------------------------------+

The Next.js and Vite plugins automatically handle port conflicts. And OAuth and webhooks get one consistent URL that works across all worktrees.

in prod

Connect to your services from anywhere (laptop, CI, etc.).

For instance, you can run a tnl publisher inside your VPC. Traffic between the tnl client and publisher uses end-to-end post-quantum encryption based on publicly trusted TLS certificates (from Let's Encrypt).

The connection will attempt P2P hole-punched UDP and fall back to using relays (which can't read your encrypted traffic). Your db or Kubernetes API aren't publicly exposed:

    tnl (your laptop)    tnl (GitHub Actions)    tnl (Node.js/Python)
            |                      |                      |
            +----------------------+----------------------+
                                   |
                +------------------+------------------+
                |                                     |
           direct UDP                             tnl relay
        (when possible)                           (fallback)
                |                                     |
                +------------------+------------------+
                                   |
+----------------------------------v----------------------------------+
|                           your private vpc                          |
|                                  |                                  |
|                            tnl publisher                            |
|                                  |                                  |
|                 +----------------+-----------------+                |
|                 v                                  v                |
|           db (e.g. RDS)                  kubernetes (e.g. EKS)      |
+---------------------------------------------------------------------+

If you can't install tnl on a client, you can give your service a public hostname and port instead. For example:

               your app or database client
                            |
                  api.example.com:15443
                   (or your subdomain)
                            v
                       tnl ingress
                            |
                +-----------+-----------+
                |                       |
           direct UDP               tnl relay
        (when possible)             (fallback)
                |                       |
                +-----------+-----------+
                            |
+---------------------------v---------------------------+
|                     your private VPC                  |
|                            |                          |
|                      tnl publisher                    |
|                            |                          |
|                            v                          |
|                        API or db                      |
+-------------------------------------------------------+

Browsers/HTTP clients can use sign-in, a share link, or a token. PostgreSQL and MySQL clients use a tnl-issued client certificate alongside their normal database credentials.

start developing

First, install the package with pnpm and initialize your project:

pnpm add -D @tnldotdev/tnl
pnpm exec tnl init
pnpm exec tnl auth login

For example, with Vite, pnpm exec tnl init adds tnl() alongside your existing plugins:

// vite.config.ts
import { defineConfig } from "vite";
import tnl from "@tnldotdev/tnl/vite";

export default defineConfig({
  plugins: [tnl()],
});

It also creates a project configuration:

// tnl.config.ts
import { defineConfig } from "@tnldotdev/tnl/config";

export default defineConfig({
  feedback: true,
  services: {
    app: {
      publicURL: {},
      target: { type: "app" },
    },
  },
});

Start your app (e.g. with vite dev) and get its URL. By default, any visitor needs to sign in or have a share link.

Hot reloading, WebSockets, SSE, and streaming responses are all supported.

Already have an app listening on port 3000? Run pnpm exec tnl publish 3000.

See installation options, the quickstart, and framework integrations.

run worktrees side by side

Once your tnl setup is committed to Git, you can leave the app running in your main checkout, and in another terminal, create a worktree and start the app there too:

git worktree add ../perf
cd ../perf
pnpm install --frozen-lockfile
pnpm dev

This would end up looking like:

your browser
|
+-- https://app-demo.example.com
|          |
|          v
|   main checkout -> localhost:5173
|
+-- https://app-demo-perf.example.com
           |
           v
    perf worktree -> localhost:5174

Vite and Next.js can choose another port when the preferred one is taken, and tnl will publish the port they actually open. Restarting either checkout reuses its URL. Read more about worktrees.

share it and get feedback

You can leave inline feedback in your app for your agent to review. Or, send someone on your team a link:

pnpm exec tnl share link create app-demo.example.com \
  --expires-in 7d

The link expires after a week and can be revoked early. Similar to how Vercel comments work, reviewers can leave inline feedback:

share link -> your app -> click an element -> leave feedback

Then you (or your agent) can use pnpm exec tnl feedback list to read feedback from the CLI. See sharing and feedback.

register your callbacks once

To add OAuth or webhook support, add the following to your config:

export default defineConfig({
  // ...existing configuration
  oauth: true,
  // and/or
  webhooks: {
    payments: {
      service: "app",
      path: "/webhooks/stripe",
      provider: "stripe",
    },
  },
});

The OAuth and webhook URLs do not change when you work across multiple checkouts. They "just work" across all your worktrees.

OAuth automatically returns the browser to the worktree that started login:

                   https://app-demo-perf.example.com
                                   |
                                   | start login
                                   v
                                 GitHub
                                   |
                                   v
+--[ oauth callback url ]---------------------------------------------+
|             https://oauth-demo.example.com/auth/callback            |
+---------------------------------------------------------------------+
                                   |
                                   | redirect browser
                                   v
                   https://app-demo-perf.example.com

Or, for webhooks, the same event fans out to all running worktrees:

                         webhook (e.g. Stripe)
                                   |
                                   v
+--[ webhook url ]----------------------------------------------------+
|            https://hooks-demo.example.com/webhooks/stripe           |
+---------------------------------------------------------------------+
                                   |
                       +-----------+-----------+
                       |                       |
                       v                       v
                 main checkout            perf worktree

You can also select a single webhook receiver, instead of fanning out. See OAuth setup and webhook providers.

connect to prod

from your laptop

For example, connect to a private PostgreSQL instance in Amazon RDS:

export default defineConfig({
  // ...existing config
  publisherGroups: {
    production: {},
  },
  services: {
    orders: {
      publisherGroup: "production",
      protocol: "postgres",
      target: {
        type: "rds",
        instance: "orders",
        region: "us-east-1",
      },
      access: { team: true },
    },
  },
});

Use your RDS instance name and region. Apply it with pnpm exec tnl apply, then run a production publisher in your VPC. From your laptop:

pnpm exec tnl connect orders

Team members use the printed connection settings with psql or their database driver and their normal database credentials. Kubernetes works with kubectl and your cluster's existing credentials.

Read about setting up private services or generating AWS publisher infrastructure.

or from ci

Let a GitHub Actions workflow connect to orders:

export default defineConfig({
  // ...existing config
  workloads: {
    migrate: {
      provider: "github",
      services: ["orders"],
      github: {
        // your GitHub repo details
        repository: "acme/demo",
        workflow: ".github/workflows/deploy.yml",
        ref: "refs/heads/main",
      },
    },
  },
});

Apply the config, then add the action to your deploy job. For example, with Drizzle:

# .github/workflows/deploy.yml
permissions:
  contents: read
  id-token: write
steps:
  # git checkout or package installation...
  - uses: tnldotdev/tnl/connect@<sha>
    with:
      workload: migrate
  - run: pnpm exec drizzle-kit migrate
    env:
      DB_PASSWORD: ${{ secrets.DB_PASSWORD }}

The action uses GitHub's OIDC with secure, short-lived tokens to connect to the orders service. Then, in your Drizzle config:

// drizzle.config.ts
import { defineConfig } from "drizzle-kit";
import { tnl } from "@tnldotdev/tnl";

export default defineConfig({
  dialect: "postgresql",
  dbCredentials: {
    ...tnl.connect("orders"),
    user: "postgres",
    database: "orders",
    password: process.env.DB_PASSWORD!,
  },
});

tnl.connect("orders") reads the local host, port, and TLS settings prepared by the action. The db password comes from GitHub secrets.

See GitHub Actions setup.

custom domains or self-hosting

You can also add a subdomain you own, for URLs like https://app.alex.dev.example.com.

Use tnl domain claim to get the DNS records to add; once verified, tnl manages its public URL DNS and certificates. See setting up a custom domain.

Or, you can even run the whole stack yourself (control, ingress, and relays), forever free. See running your own server.

how much does it cost?

The hosted tnl.dev is free for now. Accounts and teams created while it is free will keep a free plan if paid options arrive.

how does it compare?

Here's how tnl compares to Tailscale, Cloudflare, and ngrok.

in dev

tnl tailscale cloudflare ngrok
Open your app in a browser w/o installing a client Yes w/ Funnel Yes Yes
Control who can visit Sign-in, share links, or tokens Access rules w/ Serve Cloudflare Access OAuth/passwords
Where TLS is terminated Your device Your device Cloudflare Your device (but you manage certs)
Unique worktree URLs Yes Set up yourself Set up yourself Set up yourself
One dynamic OAuth callback URL across worktrees Yes Set up yourself Set up yourself Set up yourself
Send one webhook event to all worktrees Yes Set up yourself Set up yourself Set up yourself
Leave inline feedback and read it from the CLI Yes Set up yourself Set up yourself Set up yourself

in prod

tnl tailscale cloudflare ngrok
Connect without a publicly reachable endpoint tnl connect WireGuard mesh network Cloudflare One/cloudflared ngrokd or Kubernetes
Use your own domain for public HTTPS Yes No, only *.ts.net Yes Yes
Built-in web firewall (WAF) No No Yes Yes
Run the server infrastructure yourself Yes w/ Headscale No No
Route a whole subnet No, individual services Yes Yes No, individual services

license

This project is BSD-3-Clause licensed.

Directories

Path Synopsis
cmd
tnl command
Command tnl is the client entry point for tnl.
Command tnl is the client entry point for tnl.
tnld command
Command tnld runs the tnl server daemon.
Command tnld runs the tnl server daemon.
internal
benchworkload
Package benchworkload contains the publisher and visitor workloads shared by local runtime load tests.
Package benchworkload contains the publisher and visitor workloads shared by local runtime load tests.
browserfonts
package browserfonts owns the bundled Fira Code assets used by tnl browser UI.
package browserfonts owns the bundled Fira Code assets used by tnl browser UI.
client/auth
package clientauth separates ordinary authenticated requests from explicit login.
package clientauth separates ordinary authenticated requests from explicit login.
client/authority
Package authorityclient calls the authority API.
Package authorityclient calls the authority API.
client/control
Package controlclient calls the tnl control API.
Package controlclient calls the tnl control API.
client/detached
package detached owns socket-bound child processes shared by publishers and connectors.
package detached owns socket-bound child processes shared by publishers and connectors.
client/filelock
Package filelock acquires user-owned, mode-0600 regular lock files on Unix.
Package filelock acquires user-owned, mode-0600 regular lock files on Unix.
client/project
Package projectconfig finds, loads, and validates project configuration.
Package projectconfig finds, loads, and validates project configuration.
client/project/githubmetadata
package githubmetadata resolves immutable repository metadata during trusted apply.
package githubmetadata resolves immutable repository metadata during trusted apply.
client/project/init
package projectinit owns project initialization planning, safe edits, and project-local dependency installation.
package projectinit owns project initialization planning, safe edits, and project-local dependency installation.
client/project/meta
Package projectmeta validates and writes browser-safe project metadata.
Package projectmeta validates and writes browser-safe project metadata.
client/project/resolve
package resolve composes project selection with client state and current server facts.
package resolve composes project selection with client state and current server facts.
client/project/sourcestate
package sourcestate records bounded Git identifiers without saving source files.
package sourcestate records bounded Git identifiers without saving source files.
client/project/workloadmanifest
package workloadmanifest owns the nonsecret build-to-runtime workload context.
package workloadmanifest owns the nonsecret build-to-runtime workload context.
client/project/workloadsetup
package workloadsetup owns trusted workload setup and stable provider bindings.
package workloadsetup owns trusted workload setup and stable provider bindings.
client/server
package clientserver selects the control URL shared by native clients.
package clientserver selects the control URL shared by native clients.
client/state
package clientstate owns fresh v1 SQLite state, authenticated secret storage, and the transactional project journal shared by apps and publications.
package clientstate owns fresh v1 SQLite state, authenticated secret storage, and the transactional project journal shared by apps and publications.
client/supervisor
package publisherjob owns installed publications and their private state.
package publisherjob owns installed publications and their private state.
clioutput
Package clioutput renders stable human-readable CLI diagrams.
Package clioutput renders stable human-readable CLI diagrams.
config
Package config defines the versioned YAML and JSON configuration format.
Package config defines the versioned YAML and JSON configuration format.
connector/kubeconfig
package kubeconfig prepares owned contexts without selecting a global context.
package kubeconfig prepares owned contexts without selecting a global context.
connector/runtime
package connectionruntime owns one bounded connector session and its private local IPC.
package connectionruntime owns one bounded connector session and its private local IPC.
connector/stream
package stream owns connector service preparation, local listeners and stream use.
package stream owns connector service preparation, local listeners and stream use.
connector/workload
package workloadclient is the connector visitor authentication adapter for a provider workload.
package workloadclient is the connector visitor authentication adapter for a provider workload.
control/api/authority
Package authorityapi serves the built-in authority HTTP API.
Package authorityapi serves the built-in authority HTTP API.
control/api/private/ingress
Package ingressapi serves control's private API for ingress processes.
Package ingressapi serves control's private API for ingress processes.
control/api/private/relay
Package relayapi serves control's private API for relay processes.
Package relayapi serves control's private API for relay processes.
control/api/public
Package controlapi serves the control API and authorizes public URL operations.
Package controlapi serves the control API and authorizes public URL operations.
control/api/serviceaccess
Package serviceaccess projects the existing exact-service access records for both the control-session API and the signed-human authority bridge.
Package serviceaccess projects the existing exact-service access records for both the control-session API and the signed-human authority bridge.
control/certificates
Package certificates uses ACME to issue public URL and relay transport certificates.
Package certificates uses ACME to issue public URL and relay transport certificates.
control/certificates/visitor
package visitorcert owns control's client-certificate issuer.
package visitorcert owns control's client-certificate issuer.
control/dns
Package dnscontroller applies persistent DNS changes requested by control.
Package dnscontroller applies persistent DNS changes requested by control.
control/email
package emaildelivery sends queued invitation emails to a mailer.
package emaildelivery sends queued invitation emails to a mailer.
control/oidc
package oidcauth implements control-owned standard OIDC authentication.
package oidcauth implements control-owned standard OIDC authentication.
control/proxy
package controlproxy admits HTTP requests from an explicitly trusted HTTPS terminator.
package controlproxy admits HTTP requests from an explicitly trusted HTTPS terminator.
control/state
Package controlstate stores persistent control state in PostgreSQL and changes that state in transactions.
Package controlstate stores persistent control state in PostgreSQL and changes that state in transactions.
control/storagekey
Package storagekey encrypts recoverable secrets stored by control.
Package storagekey encrypts recoverable secrets stored by control.
control/webhooks
package webhookcatalog resolves bounded provider sender policies for control.
package webhookcatalog resolves bounded provider sender policies for control.
daemon/config
Package tnldconfig loads and validates tnld process configuration.
Package tnldconfig loads and validates tnld process configuration.
development/dns/cmd/dnsdev command
dnsdev is a disposable, in-memory Route 53 wire fixture and authoritative DNS server for local development.
dnsdev is a disposable, in-memory Route 53 wire fixture and authoritative DNS server for local development.
development/oidc
Package devoidc is a local development OIDC provider.
Package devoidc is a local development OIDC provider.
failure
package failure defines shared error reasons, retry policies, and safe messages.
package failure defines shared error reasons, retry policies, and safe messages.
failure/diagnostic
Code generated by scripts/generate/diagnostic-codes.ts.
Code generated by scripts/generate/diagnostic-codes.ts.
failure/problem
Package problemtype defines canonical API problem type URIs.
Package problemtype defines canonical API problem type URIs.
httpclient
Package httpclient contains shared HTTP client policy for internal clients.
Package httpclient contains shared HTTP client policy for internal clients.
httpjson
Package httpjson reads and writes size-limited JSON.
Package httpjson reads and writes size-limited JSON.
ingress
package ingress routes HTTPS by exact SNI and public services by destination.
package ingress routes HTTPS by exact SNI and public services by destination.
ingress/clienthello
Package router reads a size-limited TLS ClientHello and preserves every byte so the connection can replay it.
Package router reads a size-limited TLS ClientHello and preserves every byte so the connection can replay it.
ingress/pool
package ingresspool names the public ingress-address placement boundary.
package ingresspool names the public ingress-address placement boundary.
naming
Package naming defines public-hostname rules used by control and ingress.
Package naming defines public-hostname rules used by control and ingress.
naming/opaqueid
Package opaqueid creates and validates prefixed, cryptographically random identifiers.
Package opaqueid creates and validates prefixed, cryptographically random identifiers.
naming/tcpport
package tcpport defines network TCP port bounds.
package tcpport defines network TCP port bounds.
observability
package observability owns tnl's OTel instruments, process-scoped metrics and trace providers, bounded optional OTLP/HTTPS export, and Prometheus exposition.
package observability owns tnl's OTel instruments, process-scoped metrics and trace providers, bounded optional OTLP/HTTPS export, and Prometheus exposition.
observability/operatorlog
Package operatorlog presents typed failures in compact one-line tnld logs.
Package operatorlog presents typed failures in compact one-line tnld logs.
observability/serviceaudit
package serviceaudit defines the allowlisted service audit boundary.
package serviceaudit defines the allowlisted service audit boundary.
policy/applicationlimits
package applicationlimits owns validation shared by control and publishers.
package applicationlimits owns validation shared by control and publishers.
policy/authorization
Package authorization authorizes control operations and builds stable request hashes.
Package authorization authorizes control operations and builds stable request hashes.
policy/ippolicy
package ippolicy verifies allowed CIDRs without exposing their network addresses.
package ippolicy verifies allowed CIDRs without exposing their network addresses.
policy/publisherprovenance
package publisherprovenance validates publisher-reported deployment metadata.
package publisherprovenance validates publisher-reported deployment metadata.
policy/target
package target validates target origins and path prefixes without network I/O.
package target validates target origins and path prefixes without network I/O.
policy/tcptarget
package tcptarget validates the TCP target address used by a publisher.
package tcptarget validates the TCP target address used by a publisher.
policy/trafficlimits
package trafficlimits defines process-local encrypted visitor traffic budgets.
package trafficlimits defines process-local encrypted visitor traffic budgets.
policy/visitorlease
package visitorlease owns one scope's local visitor-policy deadline and the admissions using it.
package visitorlease owns one scope's local visitor-policy deadline and the admissions using it.
policy/visitorscope
package visitorscope names the exact resource authorized by a visitor permission.
package visitorscope names the exact resource authorized by a visitor permission.
policy/visitorsubject
package visitorsubject converts the tagged visitor principal at HTTP boundaries.
package visitorsubject converts the tagged visitor principal at HTTP boundaries.
publisher
Package publisher publishes one local service through a public URL.
Package publisher publishes one local service through a public URL.
publisher/adhoc
package adhoc owns the scoped native Go publication lifecycle.
package adhoc owns the scoped native Go publication lifecycle.
publisher/app
package clientruntime owns local app registration and publication observations.
package clientruntime owns local app registration and publication observations.
publisher/demo
package demo serves a small local HTTP app for trying a public URL.
package demo serves a small local HTTP app for trying a public URL.
publisher/group
package grouppublisher reconciles one signed publisher-group replica.
package grouppublisher reconciles one signed publisher-group replica.
publisher/identity/credentialfile
package credentialfile stores a portable publisher key and its exact grant.
package credentialfile stores a portable publisher key and its exact grant.
publisher/identity/publishingtest
package publishingtest exercises scoped native clients against signed enrollment HTTP exchanges and real publisher TLS/yamux lifecycle connections.
package publishingtest exercises scoped native clients against signed enrollment HTTP exchanges and real publisher TLS/yamux lifecycle connections.
publisher/integrations
package integrationurls maintains project integration URLs on the publisher's machine.
package integrationurls maintains project integration URLs on the publisher's machine.
publisher/localapi
package localpublisher owns the private HTTP boundary for one native project owner.
package localpublisher owns the private HTTP boundary for one native project owner.
publisher/localapi/protocol
package privateprotocol owns the bounded, machine-local SDK protocol.
package privateprotocol owns the bounded, machine-local SDK protocol.
publisher/proxy
package proxy forwards one public hostname to local HTTP or HTTPS targets.
package proxy forwards one public hostname to local HTTP or HTTPS targets.
publisher/runtime
package publisherruntime owns one explicitly deployed publisher's process identity.
package publisherruntime owns one explicitly deployed publisher's process identity.
publisher/service
package privatepublisher owns service runs, verified visitor TLS and authenticated publisher connections.
package privatepublisher owns service runs, verified visitor TLS and authenticated publisher connections.
publisher/setup
package publisherprovision owns durable group signing identity provisioning.
package publisherprovision owns durable group signing identity provisioning.
publisher/target
package publishertarget discovers exact, worktree-scoped private listeners.
package publishertarget discovers exact, worktree-scoped private listeners.
publisher/target/discovery
package targetdiscovery resolves cloud targets in the publisher's credential and network boundary.
package targetdiscovery resolves cloud targets in the publisher's credential and network boundary.
publisher/target/discovery/rdsroots
package rdsroots owns the pinned, regional Amazon RDS root trust library.
package rdsroots owns the pinned, regional Amazon RDS root trust library.
publisher/target/discovery/rdsroots/cmd/update command
command update refreshes the vendored public certificate data.
command update refreshes the vendored public certificate data.
publisher/target/kubernetes
package kubernetes owns native Kubernetes request semantics, not tunnel transport.
package kubernetes owns native Kubernetes request semantics, not tunnel transport.
publisher/toolbar
Package feedbacktoolbar serves the versioned development-only browser script.
Package feedbacktoolbar serves the versioned development-only browser script.
security/credentials
Package credentials creates and validates typed credentials.
Package credentials creates and validates typed credentials.
security/publisherproof
package publisheridentity owns publisher-held Ed25519 proofs.
package publisheridentity owns publisher-held Ed25519 proofs.
security/targettrust
package targettrust captures public CA material for publisher-to-target TLS.
package targettrust captures public CA material for publisher-to-target TLS.
security/tlspolicy
package tlspolicy owns TLS key-agreement requirements shared by native transports and publisher visitor TLS.
package tlspolicy owns TLS key-agreement requirements shared by native transports and publisher visitor TLS.
security/visitorcert
package visitorcert owns the shared client-certificate bounds and error.
package visitorcert owns the shared client-certificate bounds and error.
security/visitortoken
package visitortoken owns the signed visitor credential and local verification.
package visitortoken owns the signed visitor credential and local verification.
security/workloadproof
package workloadproof defines native workload key-possession proofs.
package workloadproof defines native workload key-possession proofs.
serviceapi
Package serviceapi provides HTTP helpers for the service APIs.
Package serviceapi provides HTTP helpers for the service APIs.
testutil/controltest
Package controltest creates named OIDC session fixtures for tests whose boundary is authorization or publishing.
Package controltest creates named OIDC session fixtures for tests whose boundary is authorization or publishing.
testutil/githubtest
package githubtest serves signed GitHub workload fixtures without allowing tests to substitute a production issuer or contact GitHub.
package githubtest serves signed GitHub workload fixtures without allowing tests to substitute a production issuer or contact GitHub.
testutil/groupdiscovery
package groupdiscovery supplies local signed control/AWS HTTPS boundaries and a verified EKS TLS target.
package groupdiscovery supplies local signed control/AWS HTTPS boundaries and a verified EKS TLS target.
testutil/managedcert
package managedcert replaces only the external CA exchange in state tests.
package managedcert replaces only the external CA exchange in state tests.
testutil/projectinit
package projectinittest supplies project fixtures for init operation and command presentation tests.
package projectinittest supplies project fixtures for init operation and command presentation tests.
testutil/visitorpolicy
package visitorpolicy supplies bounded generated-wire fixtures for policy HTTP and publisher consumer tests.
package visitorpolicy supplies bounded generated-wire fixtures for policy HTTP and publisher consumer tests.
testutil/workerobservation
package workerobservation records actual worker spans and operator diagnostics through a process-owned exporter and a local HTTPS collector.
package workerobservation records actual worker spans and operator diagnostics through a process-owned exporter and a local HTTPS collector.
transport/httpstream
package httpstream serves HTTP over one already-selected upstream connection.
package httpstream serves HTTP over one already-selected upstream connection.
transport/muxsession
Package muxsession carries multiplexed byte streams over supported transports.
Package muxsession carries multiplexed byte streams over supported transports.
transport/peer
package peer owns packet delivery for one end-to-end QUIC session.
package peer owns packet delivery for one end-to-end QUIC session.
transport/proxyproto
Package proxyproto implements tnl's strict PROXY protocol v2 boundary.
Package proxyproto implements tnl's strict PROXY protocol v2 boundary.
transport/streamcopy
Package streamcopy copies bytes in both directions and preserves half-closes.
Package streamcopy copies bytes in both directions and preserves half-closes.
transport/targettransport
package targettransport owns publisher-to-target negotiation.
package targettransport owns publisher-to-target negotiation.
transport/tunnel
Package tunnel runs tunnelv1 sessions over supported transports.
Package tunnel runs tunnelv1 sessions over supported transports.
workerloop
Package workerloop schedules bounded background-work iterations.
Package workerloop schedules bounded background-work iterations.
pkg
api/control/authority/v1
Package authorityv1 provides primitives to interact with the openapi HTTP API.
Package authorityv1 provides primitives to interact with the openapi HTTP API.
api/control/private/ingress/v1
Package ingressv1 provides primitives to interact with the openapi HTTP API.
Package ingressv1 provides primitives to interact with the openapi HTTP API.
api/control/private/relay/v1
Package relayv1 provides primitives to interact with the openapi HTTP API.
Package relayv1 provides primitives to interact with the openapi HTTP API.
api/control/public/v1
Package controlv1 provides primitives to interact with the openapi HTTP API.
Package controlv1 provides primitives to interact with the openapi HTTP API.
api/publisher/browser/v1
Package publisherv1 provides primitives to interact with the openapi HTTP API.
Package publisherv1 provides primitives to interact with the openapi HTTP API.
api/publisher/local/v1
Package localpublisherv1 provides primitives to interact with the openapi HTTP API.
Package localpublisherv1 provides primitives to interact with the openapi HTTP API.
protocol/tunnelv1
Package tunnelv1 defines messages for publisher connections and visitor streams.
Package tunnelv1 defines messages for publisher connections and visitor streams.
tnl
package tnl publishes an application-owned HTTP handler through one ad-hoc URL.
package tnl publishes an application-owned HTTP handler through one ad-hoc URL.
tests
integration/fixtures/compose-publisher command
this disposable app gives each Compose container a distinct HTTP response.
this disposable app gives each Compose container a distinct HTTP response.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL