I'm trying to find information on the syntax of the
policies.json file that is present as a key in the top-level index.js of the plugins. It is not documented here: https://github.com/reactioncommerce/api-core. Where can I find this and where is this policies info used?
@bayareacoder I used to be very confused by this as well, but I recently learned that these
policies.json files aren’t used anywhere. If I remember correctly, they were introduced with the idea to later use them with ory/keto or keycloak (don’t remember exactly), but that never happened.
this works for me https://reaction-docs-staging.reactioncommerce.com/docs/intro.html
@ahsanazeem313 what do you container logs say?
hey everyone. i have deployed reaction commernce on AWS ECS using https://university.outgrow.io/courses/802219/lectures/14600388, but i have an issue, after login into reaction-admin panel it again redirect to login-challenge.
Am I mistaken or is the new Mailchimp documentation a much reduced version of the old ReactionCommerce site? Why would the amount of documentation be reduced, instead of added and improved? Or is this just a temporary measure? In that case why is the full documentation taken offline and was not only the branding changed? Is there a link to the original RC docs, or a commitment it will stay online? Or could the staging site be deleted tomorrow? It doesn't give me much confidence if full documentation is only on a 'staging' website. Is anyone from the actual Mailchimp team on here or is this just a rogue society (in which case it does not give much confidence either...). Is this gitter channel referenced on the Mailchimp site (if not, another bad point)? If Mailchimp wants the platform to be used by third parties then solid documentation and commitment is key to compete against the e-comm market leaders. Just my $0.02. Would be good to see a reaction from a core team member about this.
hello how to create and published products using api i need to create a bulk import product from different system
@jeral997:matrix.org This plugin shows how to use the API to do bulk product import: https://github.com/outgrow/reaction-dummy-data
@bayareacoder: also how to pull this plugin in production server
How do I login so that I can add a product?
question as “how do i run this in production” i cannot answer. Pls read RC documentation first.
@bayareacoder I agree on that message you posted earlier. Let’s hope someone from the core team will chime in.
@ahsanazeem313 You should have something in your logs. Either on the admin container, the identity container or the API container. Can you tell me if there’s anything?
@bayareacoder I can’t respond to everything you said, but I just checked and the Gitter channel is linked to from the landing page of the docs
@loan-laux thanks. We are in the same boat as independent adopters. We choose a platform to build upon so besides technical capability feeling comfortable that there will be future support is key. My worry is that the focus will be on “adapters” to link captive ecomm systems (Shopify etc) with the rest of MailChimp’s marketing solutions rather than building out a standalone ecomm solution. I noticed eg that only the api is documented; nothing about the storefront.
@bayareacoder The storefront is just an example and is not meant to be a developer tool. It’ll probably get retired soon and replaced by something like Next Commerce (out:grow is building a provider for that). Open Commerce is about the API first and foremost. As a user, up to you to leverage that API from wherever you want. But I don’t see a big focus on the storefront happening in the long term.
And IMO, that’s better. “Do one thing and do it well.” That’s how you build great software. Open Commerce is headless, so the focus is on the API. That makes sense. As far as the storefront goes, the current one isn’t anything amazing, so using Vue Storefront or Next Commerce in
reaction-development-platform would actually be an upgrade.
@Akarshit thanks - i assume you work at Mailchimp. I would defnitely suggest you put all of the old docs back online. Even on the api much seems lost on real detail in the docs (eg how to extend product schema that i was looking for yesterday and suddenly found the old bookmarks i had set gone and had to come to this forum to find the docs now on a “staging” url).
@Akarshit ok - good to see you here. I would suggest you split the docs into a 'Beginner' and 'Advanced' section. Beginner should just focus on getting the reaction-development-platform up and running, first locally then in the cloud, with an example storefront UI. @loan-laux did a very good plugin to generate fake data for an example store. Then how to deploy this in the cloud; there is a very good guide with proxy-traefik to run on Digital Ocean. You can see that most of the questions here are from beginners who are very confused about basic concepts to get to this point of getting something running. Advanced doc section can then focus on going into real detail for those who want to do customizations (as we do: custom auth, custom payment methods, schema extensions etc). Then finally I would suggest to move away this forum from Gitter to a platform that enforces threads so you start building a 'wiki' per topic. We use internally ZulipChat and I believe they offer an import capability from Gitter (https://zulip.com)
Yeah I see that deploying to cloud is missing in the doc, because we didn't had a good way to do it. But I will be working on that next.
I think https://mailchimp.com/developer/open-commerce/guides/quick-start/ captures the basic of getting the setup up and running. If you feel it is missing something, let me know and I can get that added.
The point about fake data is good, we have a couple of repos to generate fake data, but maybe we should look into shipping a bunch of fake data with the product, so that people actually see something. I will definitely fly this idea.
The advanced section of the doc would be all the other guides except quick start. (again let me know if you disagree)
Moving away from gitter, haven't though about that. I will propose that and see what the community/team thinks about that.
I think https://mailchimp.com/developer/open-commerce/guides/quick-start/ captures the basic of getting the setup up and running. If you feel it is missing something, let me know and I can get that added.
The point about fake data is good, we have a couple of repos to generate fake data, but maybe we should look into shipping a bunch of fake data with the product, so that people actually see something. I will definitely fly this idea.
The advanced section of the doc would be all the other guides except quick start. (again let me know if you disagree)
Moving away from gitter, haven't though about that. I will propose that and see what the community/team thinks about that.
@Akarshit The quick-start seems good. Someone would have to go through all steps, just based on this doc, and make sure he can actually get it to run locally. On the rest, maybe it's just me but I find it just more difficult to find needed info at :https://mailchimp.com/developer/open-commerce/docs/fundamentals/ then it was at https://reaction-docs-staging.reactioncommerce.com/docs/how-to-extend-product which seems to have a much more extensive TOC in the sidebar. So hard to tell if really all detail is available in the new version.
Hey! We are in the process of upgrading Reaction Commerce from 3.2 to 3.8. Our local copies are working fine with the entire integration working properly, however during our deployment we are facing issues with graphql. Specifically,
Due to this we are unable to access Admin, and any of the plugins that depend on GraphQL. Our deployment is orchestrated through K8s.
Access to fetch at 'https://reaction-api-endpoint/graphql' from origin 'https://reaction-api-endpoint' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.Due to this we are unable to access Admin, and any of the plugins that depend on GraphQL. Our deployment is orchestrated through K8s.
7 replies
Someone here with foss ecommerce solutions experience that can recommed a project for developing a store + market place ( multi vendor functionality). For some reason they killed this in reaction :[ I'd rather donate the $7500 to open source development than throw it at cs-cart or whatever.
The only thing that was killed is the UI which was Reaction’s idea of what a multi-vendor marketplace would be… But the reality is that, if you’re building something as big as a multi-vendor marketplace, your ideas are gonna be different and you’ll need your own custom UI anyways. Hence the deprecation of the built-in UI but the continued support of the APIs.