These are chat archives for reactioncommerce/reaction
I actually went with meteor settings in the end, altough it looks weird:
settings.jsonfiles if I remember correctly. So a bit more tinkering to do to get it to work. I guess leaning on Meteor-specific mechanisms like these isn't really recommended right now given the switch in direction. May I ask why you need these to be passed to the
:3000front-end and don't want to do it programatically?
@loan-laux Yes that particular PR wouldnt solve it, as it still relies on an external json file.
Nedds to be on the frontend as the var needs to be available to the client ASAP.
I first tried passing it with a Meteor DDP Call during Meteor.startup on client and server, but that was too late.
I created multipe errors to test with, one of them was a test route that would directly throw an Error.
If the entrypoint was a different route and I would navigate to my test route, errors would be logged properly.
But if that test route was my entry point, it would fail before Sentry was initialized.
Therefore i can't rely on a DDP connection and GraphQL woul probably be the same case.
The reason I used Meteor DDP at all was that I hoped that some Meteor magic in startup( ) could serve this earlier.
shop/:slugnot work like in the back-end
reaction/.env+ creating a GraphQL query and storing it in local storage for the rest of the user's session?
shop2.yourdomain.com, or even two different domains like
someotherbrand.com. And then you pass the request URL as the shop slug, which will have to match with a shop record in your DB, and the relevant catalog will be shown.