These are chat archives for reactioncommerce/reaction
'+ modPath+ '.nodeis 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.node
is missing. Try reinstallingnode-fibers`?
meteor npm install
docker run -d \ -p 80:80 \ -e ROOT_URL="http://<your app url>" \ -e MONGO_URL="mongodb://<your mongo url>" \ -e REACTION_EMAIL="firstname.lastname@example.org" \ -e REACTION_USER="admin-username" \ -e REACTION_AUTH="admin-password" \ reactioncommerce/reaction:latest
docker-compose up -dand it’s start both containers.
docker run -d -p 27017:27017 -v /opt/mongodata:/data --name mongodb mongofeel 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
docker-compose.ymlto set up that same volume and then not be required to deal with the lengthy
# 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
volumesline in the wrong container. fixed.)
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.
masterbranch. I believe I fixed that issue where the default workflow had changed.
meteor add-platformto add iOS, Android, it should compile for you, but no startup screens, or anything special happening.