Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Daniel Hazeley
    @dhazeley
    Ya, the command I am using seems to follow this
    Daniel Honig
    @dhonig
    try? putting url in quotes?
    hydra migrate sql "postgres://hydra:changeme@postgres:5432/hydra?sslmode=disable"
    is what I used a while back according to my shell history
    @lacrx here is the other part of the service discovery that shows whats its doing in terms of internal dns/routing
    Daniel Hazeley
    @dhazeley
    I keep getting this error when I run the command that way
    unknown flag: --yes
    Error: unknown flag: --yes
    Is that flag not needed?
    Daniel Honig
    @dhonig
    its changed over time ( quickly)
    try without it
    it should just prompt you manually for a confirmation ( no big deal)
    Thomas
    @lacrx
    @dhonig thanks!
    Daniel Hazeley
    @dhazeley
    I got it working! Thanks to both of you
    Daniel Honig
    @dhonig
    cool
    @lacrx the effect of all that code is that I can say find my hydra on teh internal network by just saying
    hydra.local
    and then it gets routed to current ip of my healthy hydras in the cluster
    Daniel Honig
    @dhonig
    Anyone take a stab at implementing apple pay or paypal express in the headless setup?
    I suppose the front end has to manage all the callbacks and communicate with the backend during them over GraphQL
    Thomas
    @lacrx
    @dhonig that makes sense. since the location of these microservices is variable what with load balancing and spikes in traffic, the current location of those microservices needs to be discovered before being routed to
    Loan Laux
    @loan-laux
    @dhazeley We'll update the tutorial and remove the --yes argument. Sorry about this and glad you got it working!
    Agusti Fernandez
    @agustif
    @loan-laux Hi loan, been using the traefik-proxy proejct but having trouble with the oauth/hydra, I think the client is not starting properly or something, have opened an issue in the proxy-traefik repo
    Loan Laux
    @loan-laux
    @agustif Is the Hydra client created? You need to run the create-hydra-client.js script in the storefront to ensure that.
    Agusti Fernandez
    @agustif
    @loan-laux Yes, I managed to create the hydra-client by using docker-compose exec, like this:
      docker-compose -f docker-compose.yml exec hydra \
          hydra clients create \
          --endpoint https://hydra.my-domain.com \
          --id my-project-id \
          --secret mySecret \
          --callbacks https://storefront.my-domain.com/callback \
          -g client_credentials
    Now I have gotten rid of the errors about no hydra-client, but I just get a blank page and dont know what I am missing
    I've even tried to updating to traefik:v2 and failed miserably
    Loan Laux
    @loan-laux
    @agustif Where are you getting your blank page?
    Agusti Fernandez
    @agustif
    When I click signup/login on the storefront.
    I suspect my callback url, or env settings maybe wrong
    I've followed the SimpleDeploymentGuide.md from proxy-traefik/docs at my best
    Trying to bring back the server oonline so I can debug now
    I need to bring back my traefik to v1... 5min
    Agusti Fernandez
    @agustif
    @loan-laux onlinne nnow, https://storefront.cruceritis.com/ if you click on sign in, you get redirected to https://reaction.cruceritis.com/?login_challenge=8ccdf4d0c435468fb0d8b6f1a346e15a on a blank page
    Loan Laux
    @loan-laux
    Any logs on the backend node? Is your admin Hydra endpoint reachable?
    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
    Nuruddin Badawi
    @NuruddinBadawi
    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/.