These are chat archives for reactioncommerce/reaction

5th
Apr 2019
progranime
@progranime
Apr 05 03:32
Hi anyone experiencing this?
Error: No shipping methods are available. Even I enabled the free shipping method
Screen Shot 2019-04-05 at 11.32.02 AM.png
progranime
@progranime
Apr 05 04:42
Screen Shot 2019-04-05 at 12.41.54 PM.png
This is the error I get
progranime
@progranime
Apr 05 06:28
If anyone experience it, you can check this link to solve it reactioncommerce/reaction#2265
Alvaro Bueno
@delagroove
Apr 05 08:31
Hey guys, is there a better way to share payment API keys from the 3000 service config and have it available on the 4000 other than a GraphQL query? i wonder about that privateKey going plain, is there a way to have these as env variables to share and not expose via graphql?
Loan Laux
@loan-laux
Apr 05 08:49
Hey @delagroove! In the reaction-next-starterkit repo, check out the .env file as well as /src/config.js:30. Hopefully it'll give an idea of how to best do that.
Alvaro Bueno
@delagroove
Apr 05 08:51
thanks @loan-laux
Alvaro Bueno
@delagroove
Apr 05 09:17
that works but i was wondering if there’s a way to use the values that i set in the config of 3000, the solution there involves adding the key itself in .env, is this overkill? i thought that the 4000 was using the stripe values from there somehow
Alvaro Bueno
@delagroove
Apr 05 12:37
Any idea on how this could evolve will be welcome, right now we can go with the .env solution
Loan Laux
@loan-laux
Apr 05 12:42
Hey sorry @delagroove, I was AFK. As you can see for Stripe (which is built into RC so it's a good example), the publishable key is listed in both .env files (front-end and back-end). It's not transmitted from the back-end to the front-end, it's simply duplicated. I would advise to just go for that solution as it's way simpler, quicker and less prone to bugs.
Otherwise, you could serve your secrets from GraphQL queries, making sure to check user's permissions, but in my opinion you'd really have to have a specific use case to justify this. I think duplicating env variables on both projects is perfectly fine.
Alvaro Bueno
@delagroove
Apr 05 12:45
that’s right, i was thinking of that use case is worth of a query with those contents, thanks!
Eliot Hills
@elhil
Apr 05 14:32
anyone had any success adding debugger breakpoints within graphQL resolvers?
Loan Laux
@loan-laux
Apr 05 14:39
@elhil That's not a problem for me. What debugger are you using?
Eliot Hills
@elhil
Apr 05 16:39
@loan-laux I guess my question is, is it enough to run reaction with —inspect? e.g., in docker-compose.yml? I’m having trouble getting Chrome inspector to find it
Loan Laux
@loan-laux
Apr 05 16:40
Instead of --inspect, use --inspect-brk=0.0.0.0:9229 or --inspect=0.0.0.0:9229. You have to specify 0.0.0.0 as it will only listen to 127.0.0.1 by default, which of course would be only within the container.
Eliot Hills
@elhil
Apr 05 17:21
@loan-laux thanks so much :sweat_smile: that makes abundant sense now that you say it