James Fallon

Did you fix this? I'm getting the same problem.

Ahh, gotcha. I've got a lot to learn! Thanks for your quick reply.

Thank Chris! That's the meat of problem - how does one push up secrets to heroku or AWS or any other production server? I'm swimming in AWS documentation. The separate secrets.yml file would need to be shielded from the public. Sounds like a great future screencast! :)

No I'm using Dotenv.

I am using Stripe in development just fine, but when I push up to production on AWS, the logs are telling me "Stripe::AuthenticationError (No API key provided. Set your API key using "Stripe.api_key = <api-key>". " I am using "Stripe.api_key = ENV['STRIPE_SECRET']" which is pulling from the .env file, which is of course in my .gitignore file. So it's not pushing up to AWS as intended. How do I get Stipe production ready, as least in terms of the api key? I am using "ENV['STRIPE_PUBLIC']" in the meta tag just like the video. I'm not getting an AWS error here, which confuses me as it getting the key from .env as well. Any help would be appreciated!

anybody get this error: "Uncaught SecurityError: Blocked a frame with origin "https://js.stripe.com" from accessing a frame with origin "http://localhost:3000". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match." I'm stumped.