These are chat archives for reactioncommerce/reaction

10th
Feb 2019
Loan Laux
@loan-laux
Feb 10 05:32
Hey there @robin-lee , sorry for the late response. No way to speed up the first boot, but starting up the app afterwards should always be quicker. If you're on MacOS, Docker for Mac is known to be quite slow so it adds a bit of a burden to your workflow. If you ditch Docker (not necessarily what I'd recommend), you'll see that your startup times will be way quicker.
@bnschmdt That's a weird one. Have you tried reproducing it in local but with a dump of your dev database?
@brunaNobre Hey there, sorry for responding so late. reactionTheme.js is located at /src/custom/reactionTheme.js. I imagine you had it figured out already?
Muhammad Adil
@adilsaeed31
Feb 10 12:34
@loan-laux I am just doing installation on Digital Ocean droplet, The specs of droplet are, 1GB Ram and vCPU 1. but I am getting this error
mongodb-memory-server: checking MongoDB binaries cache...
Killedading MongoDB latest: 100 % (0mb / 0mb)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! mongodb-memory-server@2.7.3 postinstall: `node ./postinstall.js`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the mongodb-memory-server@2.7.3 postinstall 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/2019-02-10T12_34_00_512Z-debug.log
ERROR: Service 'reaction' failed to build: The command '/bin/sh -c meteor npm install' returned a non-zero code: 137
Makefile:183: recipe for target 'build-reaction' failed
make: *** [build-reaction] Error 1
Muhammad Adil
@adilsaeed31
Feb 10 13:40
@loan-laux This issue is fixed now, I resized from 1GB to 2GB but now new issue is coming. Reaction is not starting. in their logs it giving me meteor
^[[Areaction_1  | /home/node/.meteor/packages/meteor-tool/.1.8.0.1gdnmok.4nus++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/tools/cli/dev-bundle.js:119
reaction_1  |       throw e;
reaction_1  |       ^
reaction_1  | 
reaction_1  | Error: EACCES: permission denied, stat '/opt/reaction/src/.meteor/local/dev_bundle'
reaction_1  |     at Object.fs.statSync (fs.js:948:11)
reaction_1  |     at statOrNull (/home/node/.meteor/packages/meteor-tool/.1.8.0.1gdnmok.4nus++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/tools/cli/dev-bundle.js:116:19)
reaction_1  |     at getDevBundleDir (/home/node/.meteor/packages/meteor-tool/.1.8.0.1gdnmok.4nus++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/tools/cli/dev-bundle.js:36:23)
reaction_1  |     at Object.<anonymous> (/home/node/.meteor/packages/meteor-tool/.1.8.0.1gdnmok.4nus++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/tools/cli/dev-bundle.js:184:18)
reaction_1  |     at Module._compile (module.js:652:30)
reaction_1  |     at Object.Module._extensions..js (module.js:663:10)
reaction_1  |     at Module.load (module.js:565:32)
reaction_1  |     at tryModuleLoad (module.js:505:12)
reaction_1  |     at Function.Module._load (module.js:497:3)
reaction_1  |     at Module.require (module.js:596:17)

reaction_reaction_1 exited with code 1
Michael Ramos
@mdramos
Feb 10 16:13
Hello, looking for general guidance on how to use the nextjs starter kit along with the original frontend, it seems that any custom changes for admin views should be done in the "old" code, and customers will always interact with the nextjs code? --Im sure this comes up a lot, Ive just been trying to figure it out all morning and its not entirely clear
Ben S.
@bnschmdt
Feb 10 16:35
@loan-laux seemed to be tied to the fact cart review never had a if: empty state, only the cart drawer has this. So we’re working on it.