Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Agusti Fernandez
    @agustif
    Maybe I've something wrong in my storefront/reaction/hydra .env files:
    this is the hydra endpoinnt, I get a 404 pagge if I get on the root, not sure if that's expected behavior
    Restarting core attached
    to checkout logs
    Screenshot 2019-11-20 at 15.13.17.png
    everything seeems ok onn traefik's dash
    Loan Laux
    @loan-laux
    The 404 on Hydra is expected behavior indeed, @agustif
    Agusti Fernandez
    @agustif
    kay
    Loan Laux
    @loan-laux
    @agustif The backend hasn’t started yet, give it some more time
    The logs should end like this when it’s initiated:
    17:18:48.221Z  INFO Reaction: Running startup function "startup" for plugin "reaction-simple-inventory"...
    17:18:48.223Z  INFO Reaction: Startup function "startup" for plugin "reaction-simple-inventory" finished in 1ms
    17:18:48.223Z  INFO Reaction: Running startup function "startup" for plugin "reaction-pricing"...
    17:18:48.277Z  INFO Reaction: Startup function "startup" for plugin "reaction-pricing" finished in 54ms
    17:18:48.277Z  INFO Reaction: Running startup function "startup" for plugin "reaction-sitemap-generator"...
    17:18:48.410Z  INFO Reaction: Startup function "startup" for plugin "reaction-sitemap-generator" finished in 133ms
    17:18:48.410Z  INFO Reaction: Running startup function "startup" for plugin "core"...
    17:18:48.802Z  INFO Reaction: Startup function "startup" for plugin "core" finished in 391ms
    17:18:48.804Z  INFO Reaction: Reaction initialization finished: 2752ms
    Nureddin Bedevi
    @nbedevi
    Anyone knows how mutch consting deploy Reaction to meteor galaxy if there is no trafic ?
    KinhoDev
    @kinhodev_twitter
    is it safe to deploy the whole platform on rancher 2.0?
    Loan Laux
    @loan-laux
    @kinhodev_twitter I don’t see why not. Go ahead with it. :+1:
    KinhoDev
    @kinhodev_twitter
    Is there a tutorial for setting up hydra in production in kubernetes?
    Loan Laux
    @loan-laux
    @kinhodev_twitter With AWS EKS, but I guess if you read between the lines you can adapt it to any other platform: https://blog.reactioncommerce.com/deploying-kubernetes-clusters-in-aws-eks-with-the-aws-cloud-development-kit/.
    RoytenBerge
    @RoytenBerge
    dear all,
    I am trying to setup fix my authentication on my example storefront. Now on createhydraclient i get this error: getaddrinfo ENOTFOUND http://internal-bylder-hydra-admin-lb-***.eu-west-2.elb.amazonaws.com http://internal-bylder-hydra-admin-lb-***.eu-west-2.elb.amazonaws.com:80. I added the stars for privacy concerns, but they actually match my loadbalancers.
    I think i get this error because the hydra load balancers are supposed to give a 404 on a root request. Did anyone face this issue too or do you know what might be wrong in my setup?
    i used this awesome guide: https://university.outgrow.io/p/deploying-reaction-commerce-on-aws-ecs. all my tasks are running and I dont get any errors in my logs except for the create-hydra-client log in the storefront task
    RoytenBerge
    @RoytenBerge
    Also my health checks are healthy, but im using a successcode of 404 on my hydra targets, so there might be a problem in that
    RoytenBerge
    @RoytenBerge
    I fixed my issue/. One of my environment variables was incorrect
    Christopher Matuszak
    @TwixtedChaox
    hate to ask this again... but is there a simple guide to deploying to a production environment?
    lk
    @khoathanglong
    Hi all, I am new to reactioncommerce. Just want to ask what was the reason using hydra for authentication instead of others.
    Loan Laux
    @loan-laux
    Hi @kinhodev_twitter, sorry the for late response here. Hydra is open source, modern and goes straight to the point. Also, ORY has a very serious track record in terms of auth software, so the trust factor plays a big role. Keycloak would’ve been a good option too (and I think it was evaluated by the core team at some point), but Hydra does what we need in the most lightweight way.
    max
    @maxlibin

    Hi, sorry can someone help me?
    I am following this course: https://university.outgrow.io/courses/622670/lectures/11133590

    navigate to your Reaction backend directory inside your platform directory. Then, run the following command with your own repository name to start the production build.

    where is the reaction backend directory?
    I only have reaction-development-platform in my local machine.

    Loan Laux
    @loan-laux
    Hi @maxlibin, I’m the person behind this tutorial. The Reaction backend directory refers to the reaction direction in reaction-development-platform. It’s where the API is located.
    Also, keep in mind that this course was written for 2.0 and I’m rewriting it for 3.0. Most of the stuff should still work, but you’ll need to take care of deploying reaction-admin and reaction-identity yourself. Stay tuned for an updated version soon!
    In the meantime, don’t hesitate if the community can help you with this deployment. We’re here in case you get stuck.
    max
    @maxlibin
    @loan-laux thank you
    max
    @maxlibin
    Hi @loan-laux do you have eta for v3? or is there a way we can take a peek at it?
    Loan Laux
    @loan-laux
    Next week hopefully. I plan to finish it this weekend.
    Syed Shahzad Sherazi
    @S_Sherazi_twitter
    Hi Guys, I am new explorer of reactioncommerce. I have installed the development platform on aws server and trying to access FrontEnd and Backend on IP:port
    I am getting WebSocket connection to 'ws://localhost:3000/graphql' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
    in the browser. Please guide
    Loan Laux
    @loan-laux
    @S_Sherazi_twitter This should not be an issue. I don’t think GraphQL over WebSocket is fully implemented yet. The admin and the storefront should work just fine, regardless of the error.
    Keith Humphrey
    @keith-humphrey
    The outgrow.io course is very informative. I realized after getting into it, however; that is was not referencing the current codebase. I'm trying to get up-to-speed with AWS and Docker in order to figure this out, but am eagerly awaiting the 3.0 version.
    Loan Laux
    @loan-laux
    @keith-humphrey Working on it as we speak!
    eduardogonzalez479
    @eduardogonzalez479
    Hello! I hope everyone is fine, I would like to ask for help with adding a nginx (reverse proxy) layer over reactioncommerce containers, each container works perfect, but when trying to input requests on port 80, nginx redirect throws 404 in some files if not found in location / path.
    I will leave some photos .. I hope you can help me :( !!
    This is my nginx.conf

    ´´´events {
    worker_connections 1024; ## Default: 1024
    }
    http {
    default_type application/octet-stream;
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    gzip off;
    access_log off;
    proxy_buffering off;

    upstream front {
    server web:4000 max_fails=5 fail_timeout=240s;
    }

    upstream reaction {
    server 127.0.0.1:3000 max_fails=5 fail_timeout=240s;
    }

    server {
    listen 80 default_server;
    listen [::]:80 default_server;
    server_name localhost;

          location / {
            #try_files $uri $uri/ =404;
            proxy_http_version 1.1;
            add_header X-debug "URI: $host, REQUEST_URI: $request_uri" always;
            add_header X-debug2 "SERVER_ADDR: $server_addr , REMOTE_ADDR: $remote_addr" always;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
            proxy_pass http://front/;
          }
          location /api/ {
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_cache_bypass $http_upgrade;
            proxy_set_header Host $host;
            proxy_pass http://api:3000/;
          }

    }
    }´´´

    If I go to localhost / no problems, but if I go to localhost / api / graphql, in theory I should redirect to the container found in localhost: 3000 / graphql, but the default server is port 80 (localhost / graphql)
    eduardogonzalez479
    @eduardogonzalez479
    image.png
    The server is taking the port 80, instead of redirecting to 3000
    And obviously if i modify the localhost/graphql in the graphql playground to localhost:3000/graphql works fine. But this problem occurs with all containers that are not in location /
    I don't understand why it's happening
    Please help :(
    Janus Reith
    @janus-reith
    @eduardogonzalez479 There is a deployment guide using Traefik here: https://github.com/reactioncommerce/proxy-traefik/blob/trunk/README.md
    Although not nginx, I hope that might help you still