These are chat archives for reactioncommerce/reaction

26th
Mar 2015
Retic
@Retic
Mar 26 2015 03:59
I managed. Thanks was my own fault.
Aaron Judd
@aaronjudd
Mar 26 2015 15:25
with reaction 0.5.3 deployed on reactioncommerce.com, if you launch a site, and then proceed to add something to cart, go to checkout you’ll get a blank page, with error Route dispatch never rendered. Did you forget to call this.next() in an onBeforeAction?. Yet, I’m unable to reproduce this locally. Anyone else see this, or able to reproduce locally?
Spencer Norman
@spencern
Mar 26 2015 15:26
I haven't been able to produce locally on localhost, but I can produce locally on docker
Aaron Judd
@aaronjudd
Mar 26 2015 15:27
oh thanks - I’ll try that - I think I thought of that, and forget. lol. This will be a slow debug.
Spencer Norman
@spencern
Mar 26 2015 15:30
Yeah, that being said, I haven't been able to launch a docker container with my development environment
again, I'm new to docker, but I'm not sure what settings I'm missing to capture all of my local packages instead of the master branch packages that it seems to be pulling in when it builds
Aaron Judd
@aaronjudd
Mar 26 2015 15:32
ah, yes..
I’m testing that right now, but if you are doing docker build -t ongoworks/reaction . from the app dir, it should include everything including the packages dir. make sure to do ‘meteor reset’ first, clean all .build from the dir before building
Aaron Judd
@aaronjudd
Mar 26 2015 15:38
@spencern the other thing you might try - in .meteor/packages specify the version on the apps (@x.x) that will force the versions - might be needed to force it not to retrieve the published version (could be part of the problem)
Spencer Norman
@spencern
Mar 26 2015 15:40
ok, thanks. I did the docker build -t reaction/reaction-test . but did not reset first.
ok, I'll check that too, the .meteor/packages might be the trick. It seemed like that would be where it was originating. I shouldn't need to publish correct?
Aaron Judd
@aaronjudd
Mar 26 2015 15:42
nope - I do the exact same thing you are doing for the reactioncommerce site - bunch of local package in the package dir - it build just fine on docker (the reactioncommerce site is a docker meteor app)
Spencer Norman
@spencern
Mar 26 2015 15:43
perfect, thanks.
Aaron Judd
@aaronjudd
Mar 26 2015 15:44
in fact - no reason to publish packages if they aren’t going to be shared (that’s just a gentle reminder to the universe)…pffft!
lol
Spencer Norman
@spencern
Mar 26 2015 15:45
agreed lol, Atmosphere is a mess sometimes, especially when it first started. Search for anything and get seven unmaintained versions and nothing current
Aaron Judd
@aaronjudd
Mar 26 2015 16:51

@spencern

docker build -t ongoworks/reaction .
docker run --rm -p ::8080 \
   -e ROOT_URL="http://192.168.59.103" \
   -e METEOR_EMAIL="youradmin@yourdomain.com" \
   -e METEOR_USER="admin" \
   -e METEOR_AUTH="password" \
   -t ongoworks/reaction

works for me for docker local, and I have all local packages in packages (and yes, seeing the Route dispatch error - but it’s not producing a blank page)

Spencer Norman
@spencern
Mar 26 2015 16:51
thanks. I'll give that a shot in a bit
Aaron Judd
@aaronjudd
Mar 26 2015 16:52
in this case, do a docker ps to get the port that it assigned then http://192.168.59.103:49155/ as an example
Aaron Judd
@aaronjudd
Mar 26 2015 18:39
@spencern resolved that issue, and forcing a package update to our deployed version, but in general - heads up - the package system might be a little ‘whack’ as MDG is requesting everyone update packages for the windows release
Spencer Norman
@spencern
Mar 26 2015 18:46
Ok, you talking about the master branches?
Aaron Judd
@aaronjudd
Mar 26 2015 19:02
yes, forcing the package update (using @) in master - you can ignore this, but you should use the latest dev reaction-google-analytics which solves the white screen
I’ve published the ga package (0.4.4) - but when building with docker it’s getting downgraded to 4.1 which is why I’m forcing it. getting ready to head out for a long weekend - didn’t want to republish all our packages for windows, and meteor 1.1. exhausting ;-)