Skip to content
This repository was archived by the owner on Dec 16, 2025. It is now read-only.

Commit acdd2ca

Browse files
committed
Document how to work with Stripe locally
1 parent 6d32cc1 commit acdd2ca

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,22 @@ After making changes to this gem, you need to update Fizzy to pick up the change
2424
BUNDLE_GEMFILE=Gemfile.saas bundle update --conservative fizzy-saas
2525
```
2626

27+
## Working with Stripe
28+
29+
The first time, you need to:
30+
31+
1. Install Stripe CLI: https://stripe.com/docs/stripe-cli
32+
2. Run `stripe login` and authorize the environment `37signals Development`
33+
34+
Then, for working on the Stripe integration locally, you need to run this script to start the tunneling and set the environment variables:
35+
36+
```sh
37+
eval "$(BUNDLE_GEMFILE=Gemfile.saas bundle exec stripe-dev)"
38+
bin/dev # You need to start the dev server in the same terminal session
39+
```
40+
41+
This will ask for your 1password authorization to read and set the environment variables that Stripe needs.
42+
2743
## Environments
2844

2945
Fizzy is deployed with [Kamal](https://kamal-deploy.org/). You'll need to have the 1Password CLI set up in order to access the secrets that are used when deploying. Provided you have that, it should be as simple as `bin/kamal deploy` to the correct environment.

0 commit comments

Comments
 (0)