#createitcarlos-terminal-reader
1 messages · Page 1 of 1 (latest)
Hi there 👋 can you elaborate more on what you're asking? What are you trying to do with CLI?
I guess I mean, does my webhook project need to be public in order for me to get the responses about succeeded or failed if I am only running my webhooks in a local project.
I know the CLI I can pass commands in, but is it possible to run the webhook project locally and still get the webhooks to catch the physical terminal responses? BTW, I am using a Server Driven solution.
Ah, so I believe you should be able to listen for Events created on your Terminal via Stripe CLI: https://stripe.com/docs/cli/listen
Are you running into issues somewhere?
Yeh, so what I am aiming at is to have my webhooks project run locally and I am still able to be in the middle of debugging my project and for it to hit my breakpoints in the webhook code. I am not hitting the breakpoints.
I am writing my client code and need that feedback of success or fail to update the client UI.
So you're running a server locally and you have Stripe CLI setup to listen and forward events to the port that your server is running on?
In other words (if your server is running on port 3000) you run Stripe CLI with:
stripe listen --forward-to http://localhost:3000
I am trying to run the CLI for Windows. I am running the exe file from cmd line. It states it can't find Stripe
Can you post the exact error you're getting?
Yes
'stripe' is not recognzed as an internal or external command, operable program or batch file.
Though I run the exe in CMD line and it shows me the command library bhen when I try to use the command 'stripe login' (minus the quotes) it states that error
Where are you running the .exe file from in your directories? Are you running it from the same directory that the .exe file is located in? Or somewhere else in the file tree?
some where else in the file tree
I guess it is not an installation like npm or node
Try navigating to the build folder (e.g. wherever you unzipped the .zip file) and run the command again
Ah, so that worked? You can try just moving the .exe to the project folder then I suppose, if you need to be able to run it elsewhere.