I'm not maintaining this. Use a fork.

• this one has caching and integrity checking. There are others.

Tor Hidden Service Buildpack for Heroku

This buildpack sets up a Tor hidden service for your app on Heroku.

Setup

Create a Heroku app as normal, with any buildpacks you typically use. If you have a Go app, for instance, deploy it as normal.

Then:

$ heroku buildpacks:add https://github.com/apg/heroku-buildpack-tor.git

With the buildpack installed, you'll need to modify your Procfile such that the hidden service will be setup when the app runs.

web: hide <cmd you'd normally run>

While web works just fine, so too will any other process type. Use web if you want the app to be accessible generally, as well as over Tor. Use <any other type>, to avoid Heroku's router routing to your app like so:

foo: PORT=9999 hide <cmd you'd normally run>

Your app will only be accessible over Tor, through your configured .onion address.

Variables

Of course, Tor hidden services require that you provide a private_key and it's SHA, for the .onion name. You'll need to provide these as env vars:

• HIDDEN_PRIVATE_KEY: The contents of a private_key file
• HIDDEN_DOT_ONION: The onion name for the private_key.

How do you get these variables?

The easiest way is to:

$ heroku run bash
heroku$ mkdir hidden
heroku$ echo "HiddenServiceDir /app/hidden/" > tmptorrc
heroku$ echo "HiddenServicePort 80 127.0.0.1:8000" >> tmptorrc
heroku$ tor -f tmptorrc
heroku$ cat hidden/*
heroku$ ^D