Beta: The Igniter installer is new and under active testing. If you hit an issue, please open a bug report. You can always fall back to manual installation.
The Igniter installer configures tiger_stripe in a Phoenix project with a
single command. It adds config files, wires up webhook verification, scaffolds
a controller, and adds the route.
Prerequisites
Your project needs Igniter installed. If you don't have it yet:
# mix.exs
{:igniter, "~> 0.7"}Running the Installer
mix igniter.install tiger_stripe
If tiger_stripe is already in your deps, run the configuration task
directly:
mix tiger_stripe.install
Both commands do the same thing. The only difference is that
igniter.install also adds the dependency to your mix.exs.
What It Does
The installer makes five changes to your project. Igniter shows a unified diff of every change and asks for confirmation before writing anything.
1. Dev Config
Adds a placeholder API key to config/dev.exs:
config :tiger_stripe, api_key: "sk_test_YOUR_KEY_HERE"Replace this with your actual test-mode secret key from the Stripe Dashboard.
2. Runtime Config
Adds production env var config inside the if config_env() == :prod block
in config/runtime.exs:
config :tiger_stripe,
api_key: System.fetch_env!("STRIPE_SECRET_KEY"),
webhook_secret: System.fetch_env!("STRIPE_WEBHOOK_SECRET")Your deployment environment needs both variables set.
3. Webhook Plug
Injects Stripe.WebhookPlug into your Phoenix endpoint, directly before
Plug.Parsers:
# lib/my_app_web/endpoint.ex
plug Stripe.WebhookPlug, path: "/webhook/stripe"
plug Plug.Parsers,
parsers: [:urlencoded, :multipart, :json],
...The plug must come before Plug.Parsers because it needs the raw request
body for signature verification. Plug.Parsers consumes the body, so
anything after it cannot verify the signature.
If your project has multiple endpoints, Igniter will prompt you to choose which one to modify.
4. Webhook Controller
Scaffolds a controller at lib/<app>_web/controllers/stripe_webhook_controller.ex:
defmodule MyAppWeb.StripeWebhookController do
use MyAppWeb, :controller
def handle(conn, _params) do
event = conn.assigns.stripe_event
case event.type do
"checkout.session.completed" -> ...
"invoice.payment_succeeded" -> ...
"invoice.payment_failed" -> ...
"customer.subscription.deleted" -> ...
unhandled -> Logger.info("Unhandled Stripe event: #{unhandled}")
end
send_resp(conn, 200, "ok")
end
endEach event handler is a stub that logs the event ID. Replace them with your business logic. See the Webhooks guide for details on event handling patterns.
5. Webhook Route
Adds a route to your Phoenix router:
scope "/webhook" do
post "/stripe", MyAppWeb.StripeWebhookController, :handle
endThe path /webhook/stripe matches the :path option configured on the plug.
If your project has multiple routers, Igniter will prompt you to choose.
After Installation
Set your test API key in
config/dev.exs(replace the placeholder)Set production environment variables:
STRIPE_SECRET_KEY=sk_live_... STRIPE_WEBHOOK_SECRET=whsec_...Create a webhook endpoint in the Stripe Dashboard pointed at
https://your-domain.com/webhook/stripeCustomize the controller event handlers with your business logic
Test locally with the Stripe CLI:
stripe listen --forward-to localhost:4000/webhook/stripe
Re-running the Installer
The installer is safe to run multiple times:
- Config values are only added if not already present
- The controller is only created if the module doesn't exist
- The webhook plug is only injected if not already in the endpoint
If you need to reset and re-run, delete the generated controller file and remove the plug/route/config lines manually, then run the installer again.
Non-Phoenix Projects
If no Phoenix endpoint or router is found, the installer skips the plug, controller, and route steps. You still get the config changes, plus notices explaining how to set up webhook handling manually. See the Webhooks guide for the manual setup instructions.
Dry Run
Preview changes without writing anything:
mix tiger_stripe.install --dry-run