Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    contatdarpan
    @contatdarpan
    any help in this regard is highly appreciated.
    Loan Laux
    @loan-laux
    @contatdarpan That’s pretty specific. Curious to hear what type of data and traffic you’ll handle with this. Been a while since I last heard of mainframe ZOS! So I don’t know Deebezium to be honest, but I see that it provides Kafka Connect capabilities out of the box. I imagine your focus is more on processing the data in a way that makes sense to RC? Let me know more about your use case and I’ll be happy to help as much as I can.
    Amine E.
    @Am1n3
    Hello,
    Like @freewebwithme I can't get reaction-admin working in development mode. And I'm getting the same peer dependency warnings... Any ideas on how to solve this ?
    Any input would be appreciated, thanks !
    Loan Laux
    @loan-laux
    @Am1n3 Did you try to pull the latest trunk? I’m thinking Meteor 1.11 might solve your issue
    12 replies
    mohamm4d
    @mohamm4d
    hello everybody
    I am new here
    I installed the reaction-development-platform , every thing seems fine but in http://localhost:3000/ I only got Cannot GET /

    here are end of the installation with Make command:
    ..........
    Adding SESSION_MAX_AGE_MS to .env
    Adding SESSION_SECRET to .env
    Adding STRIPE_PUBLIC_API_KEY to .env
    web uses an image, skipping
    Running post-build hook script for example-storefront.
    example-storefront post-build script invoked.
    Pulling web ... done
    Creating network "example-storefront_default" with the default driver
    Creating example-storefront_web_1 ... done
    Running post-project-start hook script for example-storefront.
    example-storefront post-project-start script invoked.
    Running post-system-start hook script for reaction-hydra.
    reaction-hydra post-system-start script invoked.

    Running post-system-start hook script for reaction.
    reaction post-system-start script invoked.

    Running post-system-start hook script for reaction-identity.
    reaction-identity post-system-start script invoked.

    Running post-system-start hook script for reaction-admin.
    reaction-admin post-system-start script invoked.

    Running post-system-start hook script for example-storefront.
    example-storefront post-system-start script invoked.

    Loan Laux
    @loan-laux
    @mohamm4d There’s nothing on http://localhost:3000/. The GraphQL API is served at http://localhost:3000/graphql if that’s what you’re looking for. The storefront is at http://localhost:4000 and the admin panel at http://localhost:4080.
    mohamm4d
    @mohamm4d

    port 4000 seems to work , it should be empty as well yes ?
    I got "Sorry! We couldn't find what you're looking for.

    Clear filters"

    I expected some welcome screen on port 3000
    Loan Laux
    @loan-laux
    As I said @mohamm4d, port 3000 serves the API so you’re not gonna have any kind of UI there. The fact that port 4000 doesn’t show any products is normal as you still don’t have a shop and a catalog set up. Go to port 4080 and you’ll see the admin UI where you can do all that.
    mohamm4d
    @mohamm4d
    yep , great . thank you Loan
    mohamm4d
    @mohamm4d
    I installed reaction locally via docker ( with make command ) , where is the default admin user and pass?
    Loan Laux
    @loan-laux
    @mohamm4d There’s no default user. The first user that you register gets super-admin permissions automatically.
    Alan Ng
    @DeveloperAlan

    hey everyone, I'm having issue deploying hydra for my reaction environment to AWS via ECS. Using oryd/hydra:v1.0.8 for both hydra-public and hydra-admin. Hydra-admin is currently in it's own private subnet.

    Been following this tutorial thanks to outgrow.io: https://university.outgrow.io/courses/802219

    Hydra-admin docs looks fine at the moment, but when reaction-admin tries to connect to hydra-admin, it returns this error (via CloudWatch):

    2020-10-02T08:07:56.211+10:00    22:07:56.210Z  INFO Reaction: Waiting for Hydra service to be available...
    
    2020-10-02T08:07:56.225+10:00    22:07:56.225Z  INFO Reaction: Hydra service is available.
    
    2020-10-02T08:07:56.243+10:00    22:07:56.242Z ERROR Reaction:
    
    2020-10-02T08:07:56.243+10:00     <html>
    
    2020-10-02T08:07:56.243+10:00    <head><title>503 Service Temporarily Unavailable</title></head>
    
    2020-10-02T08:07:56.243+10:00    <body>
    
    2020-10-02T08:07:56.243+10:00    <center><h1>503 Service Temporarily Unavailable</h1></center>
    
    2020-10-02T08:07:56.243+10:00    </body>
    
    2020-10-02T08:07:56.243+10:00    </html>
    
    2020-10-02T08:07:56.243+10:00    
    
    2020-10-02T08:07:56.344+10:00    /usr/local/src/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:218
    
    2020-10-02T08:07:56.344+10:00    throw error;
    
    2020-10-02T08:07:56.344+10:00    ^
    
    2020-10-02T08:07:56.344+10:00    Error: Could not get Hydra client [503, [object Promise]]
    
    2020-10-02T08:07:56.344+10:00    at imports/plugins/core/core/server/startup/oauth.js:60:11
    
    2020-10-02T08:07:56.344+10:00    at /usr/local/src/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40
    
    2020-10-02T08:07:56.344+10:00    => awaited here:
    
    2020-10-02T08:07:56.344+10:00    at Function.Promise.await (/usr/local/src/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
    
    2020-10-02T08:07:56.344+10:00    at startup (imports/plugins/core/core/server/startup/index.js:39:3)
    
    2020-10-02T08:07:56.344+10:00    at Function.time (/usr/local/src/app/programs/server/profile.js:273:30)
    
    2020-10-02T08:07:56.344+10:00    at /usr/local/src/app/programs/server/boot.js:415:15
    
    2020-10-02T08:07:56.344+10:00    at /usr/local/src/app/programs/server/boot.js:465:7
    
    2020-10-02T08:07:56.344+10:00    at Function.run (/usr/local/src/app/programs/server/profile.js:280:14)
    
    2020-10-02T08:07:56.344+10:00    at /usr/local/src/app/programs/server/boot.js:463:13
    
    2020-10-02T08:07:56.446+10:00    

    First assumption that there is some port issue but I'm still unsure what is happening, any pointers?

    Loan Laux
    @loan-laux
    Hey @DeveloperAlan, what do you have in your CloudWatch logs for your hydra-admin service? Looks like there’s an issue there, or with its internal load balancer.
    Alan Ng
    @DeveloperAlan
    actually don't have an issue hydra-admin in CloudWatch, no particular logs stand out
    assumption is that my port configuration is all messed up on my VPC, so I'l look into it
    phearakthefoundry
    @phearakthefoundry
    Hello I have an error .
    ERROR: No such service: reaction
    After I follow this step
    cd reaction-development-platform/reaction
    git pull origin trunk
    docker-compose run --rm reaction npm install
    phearakthefoundry
    @phearakthefoundry
    This is an error on Logs in docke Containders/Apps of reaction_api_1reactioncommerce/reaction:3.10.0
    node:18) DeprecationWarning: GridStore is deprecated, and will be removed in a future version. Please use GridFSBucket instead
    (node:18) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
    TypeError: Cannot read property 'message' of undefined
    at GridFSStore.<anonymous> (/usr/local/src/app/node_modules/@reactioncommerce/file-collections/dist/common/FileCollection.js:85:78)
    at GridFSStore.emit (events.js:314:20)
    at GridFSStore.EventEmitter.emit (domain.js:486:12)
    at GridWriteStream.emitError (/usr/local/src/app/node_modules/@reactioncommerce/file-collections-sa-base/dist/StorageAdapter.js:159:28)
    at GridWriteStream.emit (events.js:326:22)
    at GridWriteStream.EventEmitter.emit (domain.js:486:12)
    at GridWriteStream.FlushWritable.emit (/usr/local/src/app/node_modules/flushwritable/lib/FlushWritable.js:37:31)
    at GridWriteStream._error (/usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:246:7)
    at /usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:265:8
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
    04:13:08.908Z INFO Reaction: Stopping Reaction API...
    (node:18) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne, or updateMany instead.
    (node:18) DeprecationWarning: collection.update is deprecated. Use updateOne, updateMany, or bulkWrite instead.
    TypeError: Cannot read property 'message' of undefined
    at GridFSStore.<anonymous> (/usr/local/src/app/node_modules/@reactioncommerce/file-collections/dist/common/FileCollection.js:85:78)
    at GridFSStore.emit (events.js:314:20)
    at GridFSStore.EventEmitter.emit (domain.js:486:12)
    at GridWriteStream.emitError (/usr/local/src/app/node_modules/@reactioncommerce/file-collections-sa-base/dist/StorageAdapter.js:159:28)
    at GridWriteStream.emit (events.js:326:22)
    at GridWriteStream.EventEmitter.emit (domain.js:486:12)
    at GridWriteStream.FlushWritable.emit (/usr/local/src/app/node_modules/flushwritable/lib/FlushWritable.js:37:31)
    at GridWriteStream._error (/usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:246:7)
    at /usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:265:8
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! reaction-api@3.10.0 start: node --experimental-modules --experimental-json-modules ./src/index.js
    npm ERR! Exit status 1
    
    npm ERR!
    npm ERR! Failed at the reaction-api@3.10.0 start script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    npm ERR! A complete log of this run can be found in:
    npm ERR! /home/node/.npm/_logs/2020-10-26T04_13_09_037Z-debug.log
    Artem Danilov
    @Izayda

    Hi! I'm trying to start reaction-development-platform on dedicated server as playground. I'm following the instruction https://github.com/reactioncommerce/reaction-development-platform

    After deploying, I'm trying to make admin user at http://server_ip:4000 The problem is, that after clicking "Create account" URL resolve as http://localhost:4444/oauth2/e.t.c

    How can I change .env variables for make scripts for dev-platform for incorrect resolving of dedicated server ip?

    balibebas
    @balibebas
    @Izayda try the proxy-traefik Ansible script to get a VPS setup (hint: go for 2GB min RAM) https://github.com/reactioncommerce/proxy-traefik
    1 reply
    You may find this tutorial helpful: https://habd.as/post/reaction-commerce-getting-started/
    Nisuga Jayawardana
    @NisugaJ

    Hi all,

    reaction-admin_1 | MongoDB replica set ready.
    reaction-admin_1 | (node:1) ExperimentalWarning: The ESM module loader is experimental.
    reaction-admin_1 | Setting up plugin imports...
    reaction-admin_1 |
    reaction-admin_1 | Failed to reset plugins file at /usr/local/src/app/client/plugins.js:
    reaction-admin_1 | Error:
    reaction-admin_1 | EACCES: permission denied, open '/usr/local/src/app/client/plugins.js'

    Any solution to fix this permission issue ?
    EACCES: permission denied, open '/usr/local/src/app/client/plugins.js' . I tried to fix it by executing sudo chown -R $USER:$GROUP /usr/local/src, but no success.

    laurent-aubry
    @laurent-aubry

    Hi, i foolowed the installation instruction from https://github.com/reactioncommerce/reaction-development-platform on windows 10 but the reaction-hydra_hydra-migrate container does not start. I have the following error :

    Config file not found because "Config File ".hydra" Not Found in "[/]""
    I guess it is linked but on the example-storefront_web (http://localhost:4000/en), I have this message : "Sorry! We couldn't find what you're looking for"

    Any idea how I can fix this please ?

    Alvaro Bueno
    @delagroove
    @laurent-aubry check the logs of each container, might not be initialized
    check february 13th logs in reaction channel,someone had same problem and there's a chain of commands there
    jameskentTX
    @jameskentTX
    Hi! There are errors during installation, make init-devcommand.
    In reaction folder, in logs ( docker-compose logs -f) there are several errors:
    Error in "afterAccountGroupCreate" consumer TypeError: Cannot read property '_id' of null api_1 | at Object.updateAccountGroup (file:///usr/local/src/app/node_modules/@reactioncommerce/api-plugin-accounts/src/mutations/updateAccountGroup.js:64:21) api_1 | at processTicksAndRejections (internal/process/task_queues.js:93:5) api_1 | at async file:///usr/local/src/app/node_modules/@reactioncommerce/api-plugin-authorization-simple/src/startup.js:60:5 api_1 | at async synchronousPromiseLoop (file:///usr/local/src/app/node_modules/@reactioncommerce/api-core/src/util/appEvents.js:24:5) api_1 | at async AppEvents.emit (file:///usr/local/src/app/node_modules/@reactioncommerce/api-core/src/util/appEvents.js:53:5) api_1 | at async Object.createAccountGroup (file:///usr/local/src/app/node_modules/@reactioncommerce/api-plugin-accounts/src/mutations/createAccountGroup.js:69:3) api_1 | at async ensureAccountsManagerGroup (file:///usr/local/src/app/node_modules/@reactioncommerce/api-plugin-accounts/src/util/ensureAccountsManagerGroup.js:14:33) api_1 | at async Object.createAccount (file:///usr/local/src/app/node_modules/@reactioncommerce/api-plugin-accounts/src/mutations/createAccount.js:88:36) api_1 | at async buildContext (file:///usr/local/src/app/node_modules/@reactioncommerce/api-core/src/util/buildContext.js:69:19) api_1 | at async ApolloServer.context (file:///usr/local/src/app/node_modules/@reactioncommerce/api-core/src/createApolloServer.js:81:7)
    jameskentTX
    @jameskentTX
    There are also type errors:
    TypeError: Cannot read property 'message' of undefined api_1 | at GridFSStore.<anonymous> (/usr/local/src/app/node_modules/@reactioncommerce/file-collections/dist/common/FileCollection.js:85:78) api_1 | at GridFSStore.emit (events.js:314:20) api_1 | at GridFSStore.EventEmitter.emit (domain.js:486:12) api_1 | at GridWriteStream.emitError (/usr/local/src/app/node_modules/@reactioncommerce/file-collections-sa-base/dist/StorageAdapter.js:159:28) api_1 | at GridWriteStream.emit (events.js:326:22) api_1 | at GridWriteStream.EventEmitter.emit (domain.js:486:12) api_1 | at GridWriteStream.FlushWritable.emit (/usr/local/src/app/node_modules/flushwritable/lib/FlushWritable.js:37:31) api_1 | at GridWriteStream._error (/usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:246:7) api_1 | at /usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:265:8 api_1 | at processTicksAndRejections (internal/process/task_queues.js:75:11) api_1 | 12:01:19.889Z INFO Reaction: Stopping Reaction API... api_1 | (node:377) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne, or updateMany instead. api_1 | (node:377) DeprecationWarning: collection.update is deprecated. Use updateOne, updateMany, or bulkWrite instead. api_1 | TypeError: Cannot read property 'message' of undefined api_1 | at GridFSStore.<anonymous> (/usr/local/src/app/node_modules/@reactioncommerce/file-collections/dist/common/FileCollection.js:85:78) api_1 | at GridFSStore.emit (events.js:314:20) api_1 | at GridFSStore.EventEmitter.emit (domain.js:486:12) api_1 | at GridWriteStream.emitError (/usr/local/src/app/node_modules/@reactioncommerce/file-collections-sa-base/dist/StorageAdapter.js:159:28) api_1 | at GridWriteStream.emit (events.js:326:22) api_1 | at GridWriteStream.EventEmitter.emit (domain.js:486:12) api_1 | at GridWriteStream.FlushWritable.emit (/usr/local/src/app/node_modules/flushwritable/lib/FlushWritable.js:37:31) api_1 | at GridWriteStream._error (/usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:246:7) api_1 | at /usr/local/src/app/node_modules/gridfs-stream/lib/writestream.js:265:8 api_1 | at processTicksAndRejections (internal/process/task_queues.js:75:11) api_1 | [nodemon] app crashed - waiting for file changes before starting... api_1 | npm ERR! code ELIFECYCLE api_1 | npm ERR! errno 143 api_1 | npm ERR! reaction-api@3.10.0 start:dev:npm run check-node-version && NODE_ENV=development NODE_OPTIONS='--experimental-modules --experimental-json-modules' nodemon ./src/index.jsapi_1 | npm ERR! Exit status 143 api_1 | npm ERR! api_1 | npm ERR! Failed at the reaction-api@3.10.0 start:dev script. api_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    jameskentTX
    @jameskentTX

    I'm using Debian 10.
    Reaction is huge and is difficult to eliminate all possible errors, but at least install process should go smoothly.
    docker-compose logs -f doesn't show install errors in other projects, only in reaction folder install process fails.
    I can enter localhost:4080 make some changes, I see mongodb using Compass and data in it, but there are errors in web application and it's impossible to use it.

    Correct install process please.

    jameskentTX
    @jameskentTX
    I've managed to install reaction project without errors as a single project using commands:
    bin/setup docker-compose up -d.
    I've created shop successfully but then errors appeared:
    WebSocket connection to 'ws://localhost:3000/graphql' failed: WebSocket is closed before the connection is established.
    and
    fe73a7c89150369a0ed67372fd013c941f824ac7.js?meteor_js_resource=true:322 TypeError: Cannot read property 'some' of undefined at v (fe73a7c89150369a0ed67372fd013c941f824ac7.js?meteor_js_resource=true:726) at Object.hasPermission (fe73a7c89150369a0ed67372fd013c941f824ac7.js?meteor_js_resource=true:726) at ReactionBlock(VariantDetailHeader-ProductHeader) (fe73a7c89150369a0ed67372fd013c941f824ac7.js?meteor_js_resource=true:726)
    I don't know what to do now. Can anybody help me?
    I should probably make some configuration changes (I'm testing app on localhost, so security issues may arise), but I don't know what to change and where. Please advice me something.
    Alvaro Bueno
    @delagroove
    @jameskentTX Im on node 12.18.3
    install process works smoothly if you have all dependencies installed (node, make, docker)
    I havent seen errors in install in a while, but another thing that happens is that api fails and the other containers keep waiting, so check for other errors as well.
    don't run them independently either, as the init-dev process will create the necessary networking for the cotainers to communicate.
    also check the RAM docker is using. i like to set more than 4gb exclusive
    jameskentTX
    @jameskentTX
    @delagroove That was excellent advice, thank you. Install process run smoothly. I registered account successfully and created shop. But when I open product page I see in console that
    WebSocket connection to 'ws://localhost:3000/graphql' failed: WebSocket is closed before the connection is established.
    And there are errors if I try to create a product:
    ReactionError: Some Products could not be published to the Catalog. Make sure the parent product and its variants and options are visible
    I'm doing something wrong probably, I'll have to read doc to understand flow of operations better.
    Thank you Alvaro for your help once more.
    jameskentTX
    @jameskentTX
    After I registered first user I see in MongoDb Compass that in Users collection, emails, verified is set to false. I didn't get an email with verification link, which I expected. Should I receive such an email?
    jameskentTX
    @jameskentTX
    What does it mean?
    INFO Reaction: Cannot publish to catalog: product has no visible variants
    Is it necessary for every product to have variants?
    jameskentTX
    @jameskentTX
    When I try to add picture to product I get error:
    WebSocket connection to 'ws://localhost:3000/graphql' failed: Error in connection establishment: net::ERR_SOCKET_NOT_CONNECTED
    It looks that client side doesn't check important thinks like price for example. I published product without price and got many errors and there is no way to correct it, as reload doesn't help. It's very frustrating.
    Alvaro Bueno
    @delagroove
    @jameskentTX every prod should have at least one variant, make sure both are visible (product and variant). Price is set at the variant label, make sure that is set along with a label for the variant. UX is tricky in the sense that both sections have a save button. save both, set visible and dont forget to publish
    if it didn't connect to 3000, check the API logs, in
    docker desktop or with docker-compose logs -f
    jameskentTX
    @jameskentTX
    Thanks Alvaro, I'll do it as you suggest. Tomorrow.
    When I was trying to build navigation tree I got error:
    "GraphQL error: No navigation tree was found"
    Ok, enough for today. I'm beat. Is not easy to use reaction app. App doesn't help and it's not intuitive. Admin have to be an expert and remember about everything.
    Alvaro Bueno
    @delagroove
    last error is beacuse the nav is empty, add at leaset one item.
    sure, everything is a process, e-commerce has its quirks, good luck
    least*
    Faiz Ahmed
    @Faiz7412
    Is anyone else facing problems with admin page? I've tried running production as well as development environment in docker and for some reason, the port 4080 shows up blank with some errors in the console.
    Faiz Ahmed
    @Faiz7412
    I'm using digitalocean droplet for deployment
    port 4100 for admin isnt loading either. In docker logs for reaction-identity it's showing
    MongoDB ready. Waiting for MongoDB replica set... no replset config has been received.MongoDB replica set ready. 05:07:51.801Z INFO Reaction: Serving Reaction Identity at http://localhost:4100
    Faiz Ahmed
    @Faiz7412
    anybody tried installing reaction on netlify?