Contents

# HTTP Tunneling with ngrok

Before your application can take advantage of features that depend on incoming webhooks, you'll need to setup an HTTP tunnel using a service like [ngrok](https://ngrok.com).

## Use a Paid Plan

You should specifically sign up for a paid account. Although ngrok offers a free plan, their $8/year or $10/month [paid plan](https://ngrok.com/pricing) will allow you to reserve a custom subdomain for reuse each time you spin up your tunnel. This is a critical productivity improvement, because in practice you'll end up configuring your tunnel URL in a bunch of different places like `config/application.yml` but also in external systems like when you [configure payment providers to deliver webhooks to you](/docs/billing/stripe.md).

## Usage

Once you have ngrok installed, you can start your tunnel like so, replacing `YOUR-SUBDOMAIN` with whatever subdomain you reserved in your ngrok account:

```
ngrok http --domain=YOUR-SUBDOMAIN 3000
```

## Updating Your Configuration

Before your Rails application will accept connections on your tunnel hostname, you need to update `config/application.yml` with:

```yaml
BASE_URL: https://YOUR-SUBDOMAIN.ngrok.io
```

You'll also need to restart your Rails server:

```
rails restart
```

Version data entries

97 entries across 97 versions & 1 rubygems

Version	Path
bullet_train-1.4.7	docs/tunneling.md
bullet_train-1.4.6	docs/tunneling.md
bullet_train-1.4.5	docs/tunneling.md
bullet_train-1.4.4	docs/tunneling.md
bullet_train-1.4.3	docs/tunneling.md
bullet_train-1.4.2	docs/tunneling.md
bullet_train-1.4.1	docs/tunneling.md
bullet_train-1.4.0	docs/tunneling.md
bullet_train-1.3.25	docs/tunneling.md
bullet_train-1.3.24	docs/tunneling.md
bullet_train-1.3.23	docs/tunneling.md
bullet_train-1.3.22	docs/tunneling.md
bullet_train-1.3.21	docs/tunneling.md
bullet_train-1.3.20	docs/tunneling.md
bullet_train-1.3.19	docs/tunneling.md
bullet_train-1.3.18	docs/tunneling.md
bullet_train-1.3.17	docs/tunneling.md