reactioncommerce / reaction-questions Goto Github PK

Is it possible to share a detailed plan for the coming 6-12 months?
This we can have an idea about what's coming and plan accordingly.

Can we add new content block making ability in Operator side to show up on store front ui?

Demeteorization of the API as in being able to run the GraphQL API (not necessarily the Operator UI) as a pure Node.js app.

When the GraphQL API will be just a Node app, am I understanding correctly that the Operator UI will continue to be on Meteor for a while?

If that is the case, what is your plan on the user management side of things during this stage? Will the Node.js GraphQL API be the IDP? Or will Meteor stay the IDP for a while, even though the API is on Node? Or will a separate, neutral IDP service be introduced? Asking for both for the Operator UI users and customer users, in case you plan to split them.

Thanks!

About multi shop in reaction: I know that's possible to create more than one shop per installation(I'd love to have a tutorial or a video showing how to do that since there's no UI currently available for it), I'd like to know if this shops are independent in a way that I can create for an example: 3 shops for 3 different clients where none of them will be able to see each other products or any items in the panel and be able to manage all those clients through a single admin account, all of them will consume the same back-end API but they will have their own front-end applications running on their own domains. Is this scenario currently possible in reaction?
I'd also like to know which of those item are separate in multi shop scenarios(each client can have their own configuration):Payment providers, fulfillments and products.

Hey all,

I am committed to continue using Reaction for small business clients and I am trying to estimate the running costs for v2.

The v2 docs Deployment guide recommend 2g of memory for Node and Reaction to run well. Now that the Reaction app is solely an Operator environment, does this recommendation still stand? Also, what is the recommendation for deploying the Example Storefront?

For v1 shops I have used Galaxy + Compose.io but I am hoping with the lighter headless approach I can reduce running costs and partly self-manage my instances.

Any suggestions from the core-team or open-source devs with their own experiences with v2 super welcome! Looking forward to the Q+A.

best,
O

What's Reaction's plan to engage with the community in the future?
Are you planning to write technical posts about best practices?
Videos covering technical subjects similar to Gatsbys?
What about communication? Communicating with Reaction team through the chat is very hard because it's so random. Maybe a community evangelist who actively engage and respond with the community?

I am trying to understand authentication, went through the docs.. my understanding so far is meteor is handling the authentication & not graphQL, & I have installed simple:rest-accounts-password & see the token being return, but still clueless where exactly the authentication is taken place in the code

Hello!

Is example-storefront proprietary? Or can we use it as starting point and keep the same design?

Best regards,
Gonçalo

Wanted to check if we could use Keycloak instead of Hydra as our OAuth 2.0 and Open ID Connect Provider? Our organization already uses Keycloak and would like to use the same for the other applications as well.

Thanks,
Shashi

Hello! First of all, thank you for hosting this session!
I have a couple questions regarding Hydra's authentication:

When do you expect to have a production ready version of authentication?
If you do not have a roadmap for this, what are the main concerns of Hydra not being safe for production?
If I want to launch my online shop next month, what should I change in terms of authentication?

Best regards,
Gonçalo

navigation drag and drop not worked? How to solve this?