Install Reacher in 20min
Reacher is designed for seamless self-hosting, giving you full control over its operation on your infrastructure. This guide demonstrates how to install and run Reacher on your local computer in under 20 minutes, using a Dockerfile that is provided you as part of the Commercial License Trial.
Prerequisites
An account on https://reacher.email (required for the Commercial License Trial and access to the Dockerfile).
Docker installed on your system (follow the Docker installation guide for your OS).
Tutorial Scope: Install Reacher on your local computer
Reacher’s stateless architecture enables easy horizontal scaling by deploying multiple containers, each running a Reacher instance for parallel email verifications. However, for simplicity, this tutorial focuses on a local installation. A further section focuses on Scaling for Production.
The provided Dockerfile includes a pre-configured proxy, resolving the common ISP restriction on outgoing requests to port 25 used by Reacher to perform SMTP verifications.
Step-by-Step Tutorial
Navigate to the Commercial License Trial tab of your Reacher Dashboard (go there directly). You'll see a command to run Reacher's latest (v0.10) Docker image:
Replace <YOUR_UNIQUE_TOKEN>
with your unique API token shown in the dashboard.
Expected output:
If you see an error message, such as Error: missing field `api_token`
, double-check the -e RCH__COMMERCIAL_LICENSE_TRIAL__API_TOKEN
flag you passed. If you see other errors, either try Debugging Reacher or send an email to amaury@reacher.email.
Advanced users can also set additional Reacher Configuration.
Verify an email by running the following command in another terminal.
Advanced users can pass additional configuration fields to the /v1/check_email endpoint.
If successful, you'll see JSON object with an
is_reachable
field.
You can read more about all the fields in Understanding "is_reachable".
If this step hangs for a long time, or returns a JSON result with is_reachable="unknown"
, see Debugging Reacheron how to fix this.
If you go back to check the terminal with the Docker command, you should see corresponding logs:
Congratulations! You just successfully verified an email from your computer. Now it's time to think about Scaling for Production.
Troubleshooting
If you have any issue in one of the steps above, you can try Debugging Reacheryourself, or send me an email amaury@reacher.email.
Last updated