Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    MitchellWT
    @MitchellWT
    Hey, I'm attempting to deploy an online development platform using digital ocean. I'm using this github repo https://github.com/reactioncommerce/proxy-traefik. The installation works fine until I perform a "make init-dev", after that point all web addresses (except the traefik dashboard) respond with traefik's "404 page not found" page. I think the issue is that traefik can't locate the new files. So I'm wondering where I can find where traefik determines the file locations for web addresses?
    2 replies
    l2ysho
    @l2ysho

    The db user has admin privileges, what I'm doing wrong please help.

    Hi, you need also clusterAdmin and dbAdmin roles for your user

    Robin T
    @qispark
    Hi there, I was wondering if anyone encountered an issue with Reaction Admin using a production Reaction server. In my docker instance, when I point it to my Reaction server running on localhost in docker, it works. However, it seems like it's unable to generate a valid token when configured with a remote production Reaction server, causing the user to log out after having just logged in. Just wondering if anyone has encountered such an issue and what sort of misconfiguration may cause this?
    2 replies
    vaneet
    @zmcomputing
    Hi Everyone, I have two VPS hosts at contabo. Can I deploy reaction commerce services on both ? . Which Services you recommend to install on two for best scalability and performance ? Also, I cannot find deployment on production documentation. I can see environment variables, if all these values in env files need to be changed for prod, then it should be fine, but I suppose there should be other configuration parameters for running on production for instance caching and etc. Thank you.
    Thomas
    @lacrx
    for the EXTERNAL_GRAPHQL_URL env variable in reaction commerce 2 frontend, is that our backend url, followed by "graphql-beta"?
    just making 100% sure. the INTERNAL_GRAPHQL_URL is the backend load balancer dns name followed by "graphql-beta", so i'm pretty sure the EXTERNAL_GRAPHQL_URL follows that same format. i'm just not 100% sure
    vaneet
    @zmcomputing
    So, where can I get some help on setting reaction on VPS in production ?
    Loan Laux
    @loan-laux
    Hey @zmcomputing, there’s a tutorial that you can follow here: https://github.com/reactioncommerce/proxy-traefik. Let me know if you have any questions.
    vaneet
    @zmcomputing
    Thank you Loan, I have followed the tutorial. however that is to deploy on digital ocean and I see that it expects authentication token for its api aka droplet. How can I simulate or create that on my Centos 7 VPS
    I read in detail about cloud computing and realised that cloud servers are well designed at hardware level for virtualizations and running many softwares on top to enable scaling and I cannot do that on two VPS as it need dedicated servers to simulate. Therefore, can I install reaction commerce on two VPS , if yes, then what is best configuration. as some services will run inside docker on one machine and database and etc on other VPS. Their communication will be via external ip of other VPS . as I dont think I will get internal IP from hosting provider for the VPS to sort of have in same tenant. Does that make sense or perhaps I am just over analysing here ? Thank you again
    Loan Laux
    @loan-laux
    @zmcomputing You can run RC on multiple VPS using Docker Swarm and Portainer. You’ll find plenty of tutorials online to set this up. Pretty much gives you all the advantages of a managed platform like ECS, but with your own infrastructure.
    vaneet
    @zmcomputing
    @loan-laux : That is so helpful :) thank you very much. ( I can setup above on my VPS this week, I assume then with above setup, I could create a auth token for connecting service running on one VPS ( which is expected here : https://github.com/reactioncommerce/proxy-traefik ) and in this way I can manage to install reaction commerce on two VPS in production. I can put a blog post/ article after doing it and it can help many other startups and techies to use this platform. I researched a lot but could not find any article to setup reaction commerce on VPS. Thank you again :)
    Loan Laux
    @loan-laux
    Glad I could help @zmcomputing. As far as articles go, in addition to the tutorial I sent you, @balibebas wrote a blog post about his own experience deploying RC on a VPS. Hope that helps you more. https://habd.as/post/reaction-commerce-getting-started/
    vaneet
    @zmcomputing
    Yes, That uses digital ocean where they have droplet which is VPS cloud compliant, and they expect : do_auth_token The Authentication token for the Digital Ocean API.
    As per your suggestion, I should be able to set up with Portainer and DockerSwarm.
    aliabrak
    @aliabrak
    Hi everyone, Would be great and much appreciated if someone can create a virtualbox or vmware image which works out of the box to get up and running (for developement) as quickly as possible.
    Loan Laux
    @loan-laux
    Hey @aliabrak. Wouldn’t Docker work? There are ready-to-use images available on Docker Hub, which you can set up easily with the Makefile at https://github.com/reactioncommerce/reaction-development-platform.
    m5ingh
    @m5ingh
    how do i add new shop to my docker reaction installation.
    details
    i have tried to register as new user and add another shop using a new account for adding shop but after clicking regiester shop nothing happerns.
    also if i understand correctly there must be overall owner of entire reaction installation only who can add or delete shops. is this correct or am i wrong?
    Akarshit Wal
    @Akarshit
    The first user you create is the owne of the whole reaction. If you login as that user, you should be able to create new shops
    m5ingh
    @m5ingh
    i was unclear regarding the details i provided:
    i have the first account tied to a shop
    when i try to add new shop in the same first created account after enterring shop name and clicking create shop nothing happens
    Akarshit Wal
    @Akarshit
    Hmm weird, I don't see that. I will get reaction running and try that again now..
    m5ingh
    @m5ingh
    exact steps i took:
    logout and login
    Loan Laux
    @loan-laux
    @m5ingh What versions of reaction and reaction-admin are you using?
    m5ingh
    @m5ingh
    see default shop. click add new shoop, give name, click create shop
    admin:3.0.0-beta.11
    reaction:3.11.0
    Loan Laux
    @loan-laux
    I believe beta 12 is available now… Can you update just to be on the safe side? I assume you’re just trying to run the platform with no modification so that shouldn’t be an issue. Right?
    m5ingh
    @m5ingh
    yes
    i will update and inform
    Loan Laux
    @loan-laux
    Same for the API, we now have 3.11.1. A very minor release, but still good to be up to date.
    m5ingh
    @m5ingh
    something weird is happening. i deleted the previous reaction repo after stopping the containers. fresh clone and make. even then the previous accounts are showing up. is this has something to do with cookies
    the accounts created in previous installation shouldnt show up in fresh cloned and built system
    -7/4
    m5ingh
    @m5ingh
    is there some docker cache that has not been cleard?
    m5ingh
    @m5ingh
    i did make clean. redid make. storefront shows no previous data, admin is refusing connections
    m5ingh
    @m5ingh
    admin too is free from previous data, and even now after adding the first account and adding the first shop , nothing happens after i click new shop, name and click create shop.
    m5ingh
    @m5ingh
    @loan-laux after going through documentation i found out that reaction doesn't support multi shop setup out of the box. i would really be thankful if i could get directions on how one should go about implementing multi shop set up in base reaction containers. i am willing to put in additional development work and make the source available for all.
    Loan Laux
    @loan-laux
    @m5ingh The API actually support multi-shop usage out of the box. The docs warn that there’s no full-circle, end-to-end support for marketplaces (as in, the admin UI won’t necessarily have all the features you’d want from a vendor UI, and the example storefront is single-shop only). But these are UIs, and you’re supposed to replace them with your own anyways. As far as the API goes, everything you need should be there.
    Sebastian Franco - Devops Engineer
    @jhonsfran1165
    @m5ingh if you want multi-shop support you also have to take a look at the hydra implementation. If you want to support multiple shops you have to create a hydra client record for each shop you want to connect to the API to grant access to each shop to generate access tokens. That's one of the biggest problems when you are dealing with multi tenant architecture. Also, keep in mind that your tenant ID is the shopId, so you can identify each tenant with that.
    m5ingh
    @m5ingh
    @loan-laux @jhonsfran1165 huge shout out to both of you for all your help. I have a question. As i understand reaction admin is being replaced with admin that will have lego like structure for core, etc. basically replacing meteor parts. does this mean that reaction identity which also has meteor parts are being replaced? i ask this because i want to have clarity if i should do multi shop work on reaction-admin or the upcoming admin alongwith hydra and identity
    Sebastian Franco - Devops Engineer
    @jhonsfran1165
    I'm not sure, maybe @loan-laux has more context about that. What I know is the identity service can get a lot better. Right now is using meteor but in my way of think, if the reaction team is going to create another admin the identity service also has to be replaced. I was thinking to use ORY kratos and ORY keto to create a universal login that allows me to handle permissions and user management cleaner. I know is a little complex but I like to use the ORY ecosystem.
    Loan Laux
    @loan-laux
    @m5ingh I agree with @jhonsfran1165 on all the points here. As far as what’s planned: AFAIK, discussions are happening on a new auth system. No decisions made now, but it’s starting to be discussed.
    B D
    @bayareacoder
    Interesting discussion. We also have a potential need to go to multi-shop from a single Docker deployment i.e. 1 Hydra instance would need to give tokens for multiple storefronts. Right now we have done our own admin integrated with the Firebase custom auth system we use. We developed our own admin with logins integrated with our auth system that uses "Firebase custom token" auth flow for "store owner/manager" accounts. When such a user signs up on our system, we write directly into the reaction MongoDB collection to create the user there as well (not using Hydra). Since the user will be auth with a token from Firebase, we developed reaction api middleware to check the token with Firebase. To ensure compatibility with example-storefront where we use the existing reaction Hydra auth for "shopper" user accounts, we basically add our token from our admin client under another HTTP header. When the middleware detects that header, it will use Firebase for auth check; when it sees the reaction token header it will use the original reaction Hydra check. So how to support multiple shops for a retail chain (assume within same Docker container) that can be controlled from same admin in this case? Seems as simple as making a single reaction user owner of multiple shops, and then creating multiple storefront instances in the Docker container, each with its own subdomain (store1.<domain>, store2.<domain>) or am I missing something? The only issue I see is that shoppers would need to create separate accounts for each shop. Not sure if the current user schema would allow a shopper user account to be associated with multiple shops?
    I guess ours is not a "marketplace" (1 storefront covering multiple shops) but a "single-chain multi-shop" (multiple independent storefronts that are centrally managed) scenario.