Create the .env files from the examples with the following commands:
# setup environment variables
$ cp ./frontend/.env.example ./frontend/.env
$ cp ./backend/.env.example ./backend/.env
Then, update the following env variables inside the ./backend directory:
# stripe account secrets
STRIPE_API_KEY=sk_test_your_secret_key_
STRIPE_WEBHOOK_SECRET=whsec_your_webhook_secret
- Run the backend and frontend at the same time with Docker Compose:
# running project with all dependences
$ docker-compose --env-file ./backend/.env up
- Use Stripe CLI to listen for events:
# forward events to localhost
$ stripe listen --forward-to http://localhost:5000/stripe-events
Events will fail if the card is not present at the database, so you need to register in the home screen ( http://localhost:3000). Here you should enter the same ID present in your Stripe Dashboard (e.g. ic_1Pb...). Afterwards, you will be redirected to your personal card dashboard.
The container will log to the terminal, besides this you can use some software like DBeaver to see the rows generated for the Postgres database. For event monitoring, you can access the http://localhost:5000/queues endpoint.