#createitcarlos-terminal-reader

1 messages · Page 1 of 1 (latest)

frosty ruin
#

Hi there 👋 can you elaborate more on what you're asking? What are you trying to do with CLI?

lone garden
#

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.

frosty ruin
#

Are you running into issues somewhere?

lone garden
#

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.

frosty ruin
#

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

lone garden
#

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

frosty ruin
#

Can you post the exact error you're getting?

lone garden
#

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

frosty ruin
#

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?

lone garden
#

some where else in the file tree

#

I guess it is not an installation like npm or node

frosty ruin
#

Try navigating to the build folder (e.g. wherever you unzipped the .zip file) and run the command again

lone garden
#

is it location based run?

#

Welp that was is to get the CLI to run, thank you

frosty ruin
#

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.

lone garden
#

yes that worked. It is path specific not system wide

#

I see now