Closed DavidVII closed 3 years ago
It looks like hackney was updated last month to version 1.15.2
, which fixed a bug where SSL requests would break. This makes sense since my local machine doesn't use SSL, but production does.
The fix was to run mix deps.update hackney
to update hackney in the lock file to 1.15.2
.
Everything works as expected after doing that and pushing to production.
Not sure if there's anything we need to do here since it's not an issue with this adapter, but maybe it'd be nice to use the latest version of hackney? Not really sure.
Here's the related issue on hackney: https://github.com/benoitc/hackney/issues/591
Hello there, I am getting the following error, but it doesn’t really provide any insights into what the error actually is and I, therefore, can't figure out how to go about fixing it.
Running this code triggers the following error:
The API key is present in the env and I’m able to pull it up using
System.get_env(“MY_API_KEY”)
. To make things extra fun, everything works as expected in development, but not in production even though dev/prod share the same configuration in this case.In
config.exs
Any pointers here would be greatly appreciated. I'd be open to opening a PR up if necessary, but perhaps I'm just missing something?
Thanks for your time 😊