These are chat archives for reactioncommerce/reaction

26th
Jul 2016
3Maestros
@3Maestros
Jul 26 2016 07:56

I'm not able to get reaction work on Windows 10. It gets stuck in the init (reaction init) on following step: > fibers@1.0.13 install c:\Projects\reaction\node_modules\fibers

node build.js || nodejs build.js

And after that, when i try to run reaction, I get following error: => Started proxy.
=> Started MongoDB.
W20160726-00:13:40.922(-7)? (STDERR)
W20160726-00:13:41.081(-7)? (STDERR) c:\Projects\reaction\node_modules\fibers\fibers.js:16
W20160726-00:13:41.081(-7)? (STDERR) throw new Error(''+ modPath+ '.node is missing. Try reinstalling node-fibe W20160726-00:13:41.081(-7)? (STDERR) ^ W20160726-00:13:41.081(-7)? (STDERR) Error:c:\Projects\reaction\node_modules\fibers\bin\win32-ia32-v8-3.14\fibers.nodeis missing. Try reinstallingnode-fibers`?
W20160726-00:13:41.081(-7)? (STDERR) at Object.<anonymous> (c:\Projects\reaction\node_modules\fibers\fibers.js:16:8)
W20160726-00:13:41.081(-7)? (STDERR) at Module._compile (module.js:456:26)
W20160726-00:13:41.081(-7)? (STDERR) at Object.Module._extensions..js (module.js:474:10)
W20160726-00:13:41.081(-7)? (STDERR) at Module.load (module.js:356:32)
W20160726-00:13:41.081(-7)? (STDERR) at Function.Module._load (module.js:312:12)
W20160726-00:13:41.081(-7)? (STDERR) at Module.require (module.js:364:17)
W20160726-00:13:41.081(-7)? (STDERR) at require (module.js:380:17)
W20160726-00:13:41.081(-7)? (STDERR) at Object.<anonymous> (c:\Projects\reaction.meteor\local\build\programs\server\boot.js:1:75)
W20160726-00:13:41.085(-7)? (STDERR) at Module._compile (module.js:456:26)
W20160726-00:13:41.085(-7)? (STDERR) at Object.Module._extensions..js (module.js:474:10)
=> Exited with code: 8
I have spent hours to fix this. Please HELP!!!
hrath2015
@hrath2015
Jul 26 2016 08:12
run again
remove the line corresponding to fibers form package.json. Hope u have done meteor npm install
sequence got interchanged
first remove then run
hrath2015
@hrath2015
Jul 26 2016 10:22
@jshimko below command assumes hosted mongodb instance. if need a local instance what change I need to make.
docker run -d \ -p 80:80 \ -e ROOT_URL="http://<your app url>" \ -e MONGO_URL="mongodb://<your mongo url>" \ -e REACTION_EMAIL="youradmin@yourdomain.com" \ -e REACTION_USER="admin-username" \ -e REACTION_AUTH="admin-password" \ reactioncommerce/reaction:latest
Please let me know thanks
Jeremy Shimko
@jshimko
Jul 26 2016 13:06
@hrath2015 There is no local Mongo in production. You can run one in a container and use Docker Compose to link them though. The config already exists…
https://github.com/reactioncommerce/reaction/blob/master/docker-compose.yml
Just run docker-compose up -d and it’s start both containers.
hrath2015
@hrath2015
Jul 26 2016 13:12
thanks
Ryan Watts
@rwatts3
Jul 26 2016 17:19
How do I insert tax information ?
Mike Murray
@mikemurray
Jul 26 2016 17:21
@rwatts3 we're currently working on the tax module to be released mid august
Ryan Watts
@rwatts3
Jul 26 2016 17:21
is there anyway to manually add tax information ? It's a bit confusing because it shows tax on the checkout process so I at least for the time being need to put something in that field
client most likely will not change the tax rate at all as his market is local
Aaron Judd
@aaronjudd
Jul 26 2016 17:25
@rwatts3 I’m actually working on it this week, but you could hard code it in the cart transforms. https://github.com/reactioncommerce/reaction/blob/d569c68747a184a71c07c1e3e6ef0f48b525cd57/lib/collections/helpers.js#L35
line 55, add tax, done. ;-)
Ryan Watts
@rwatts3
Jul 26 2016 17:25
awesome thank you
Ryan Watts
@rwatts3
Jul 26 2016 17:32
@hrath2015 this will get a quick running mongodb instance with persistent data locally docker run -d -p 27017:27017 -v /opt/mongodata:/data --name mongodb mongo feel free to change the path to anywhere on your server you'd like. Believe me having the persistent data is extremely useful especially with all the changes docker has been doing which some may cause you to blitz docker altogether at least your dbs and collection data will still be available should you spin up mongo again, if you want mongodb only accessible via your server and only to be shared with apps running on your server then set -p 127.0.0.1:27017:27017
locally as in on your server *
In the past month i've literally blitzed and reinstalled mongodb due to docker trials and errors at least 20 times and none of my client data was lost
Jeremy Shimko
@jshimko
Jul 26 2016 17:33
You could add one line to the existing docker-compose.yml to set up that same volume and then not be required to deal with the lengthy docker run commands.
# Usage:
# docker-compose up -d

reaction:
  image: reactioncommerce/reaction:latest
  links:
    - mongo
  ports:
    - "80:80"
  environment:
    ROOT_URL: "http://anything.com"
    MONGO_URL: "mongodb://mongo:27017/reaction”

mongo:
  image: mongo:latest
  command: mongod --storageEngine=wiredTiger
  volumes:
    - /opt/mongodata:/data
Ryan Watts
@rwatts3
Jul 26 2016 17:35
@jshimko You are the man !
Jeremy Shimko
@jshimko
Jul 26 2016 17:35
docker-compose up -d
Ryan Watts
@rwatts3
Jul 26 2016 17:35
that's definitely the preferred way to go.
hrath2015
@hrath2015
Jul 26 2016 17:36
thanks a lot
Jeremy Shimko
@jshimko
Jul 26 2016 17:36
that file will work as-is, by the way. Just add your ROOT_URL.
Ryan Watts
@rwatts3
Jul 26 2016 17:36
I can't stress the importance of persistent data enough, also some people preach using data volumes but I advise against it in some cases because majority of the time when you run into errors or issues with docker people say in the forums to blitz the .docker folder, when you do that you actually destroy the mapping to your volume paths which would have been where your data was stored if you chose to use a data volume
In essence any database mysql or mongodb always use a direct mapping to your server somewhere
Jeremy Shimko
@jshimko
Jul 26 2016 17:37
Yep. If you care about the data at all, persist it to the disk.
That way you can completely throw away your containers and they’ll always come right back up
(sorry, I put the volumes line in the wrong container. fixed.)
Owen Hoskins
@owenhoskins
Jul 26 2016 20:25

Got a Q regarding the development BeesKnees customization tutorial: I cloned the BeesKnees github repository and following the guide I added it to the development branch of Reaction from last week. Everything seems to function normally except the routes are quirky:

1) Directly hitting the index path displays as expected. However, clicking a product brings you to a 404 page. Returning to the index via the back button and then clicking on the same product shows that product as expected.

2) Refreshing the browser on that same product shows a 404 page each time.
@zenweasel: Got any idea what might cause behavior like this? From logging Reaction.Router._routesMap I can see the routes as expected.

Brent Hoover
@zenweasel
Jul 26 2016 20:41
I think you will want look at the recent updates I made on the master branch. I believe I fixed that issue where the default workflow had changed.
Owen Hoskins
@owenhoskins
Jul 26 2016 20:43
Ok, I'll check that out tomorrow, thanks!
3Maestros
@3Maestros
Jul 26 2016 20:53
Is reaction mobile ready? Can I run it as a App on my Android or IPhone? Anyone tried it?
Aaron Judd
@aaronjudd
Jul 26 2016 23:21
@3Maestros native or web? we’ve been testing it in mobile since day one as a responsive app. I’ve compiled an IOS build a few times, but we’ve not published any of the config for that and it’s been a while so probably a from scratch effort.
you can use meteor add-platform to add iOS, Android, it should compile for you, but no startup screens, or anything special happening.