You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use ${.env:PHONE} to access environment variables (supports .env files).
How stripe knows which .env file to read? Generally we commit .env file with some examples with empty values, and the real values are set in .env.local, .env.test etc.
Expected Behavior
It should read the PRICE_ID from my .env or .env.local, .env.test etc.
Environment
Windows
The text was updated successfully, but these errors were encountered:
@sovetski In my case the Stripe.CLI my fixture and .env file all live in the same directory. When running the command I think it uses the file in that directory.
Issue
I am running
stripe fixtures ./fixtures.json
, and it returns:I have
PRICE_ID
set in my.env
and.env.local
file.My
fixtures.json
is:I followed the explanation from official documentation: https://docs.stripe.com/cli/fixtures
It says:
How stripe knows which
.env
file to read? Generally we commit .env file with some examples with empty values, and the real values are set in.env.local
,.env.test
etc.Expected Behavior
It should read the PRICE_ID from my
.env
or.env.local
,.env.test
etc.Environment
Windows
The text was updated successfully, but these errors were encountered: