These are chat archives for SciSpike/yaktor

11th
Nov 2016
justinr1234
@justinr1234
Nov 11 2016 17:41
Heads up I had an issue following the startup when on Node 6.8.1 ... Switched to 4.2.1 and am able to continue running the command ./yak gen-src gen-views start
Also looks like all subdomains of yaktor.io are not working ... such as eclipse.yaktor.io and docs.yaktor.io
Matthew Adams
@matthewadams
Nov 11 2016 17:45
Good to know — thanks. We’ll look into official Node 6.x support in the future.
Yeah, you’re prolly using OpenDNS. If you switch to another dns service (like Google DNS), it should work. We’re working with AWS & OpenDNS to fix that.
justinr1234
@justinr1234
Nov 11 2016 17:46
Seeing issues with the DNS ... can't get to anything by IP or by the http://www.myapp.yaktor ... any common causes? Trying to debug now ... Looks like all my containers are running properly (dns, vpn, mongo, app) (on Mac)
Matthew Adams
@matthewadams
Nov 11 2016 17:48
What version of yaktor are you using? Latest is 0.60.1.
justinr1234
@justinr1234
Nov 11 2016 17:49
Just pulled whatever is on github and followed tutorial here: https://github.com/SciSpike/yaktor
Just didn't know if people hit issues with connecting to the node server after getting up and running with the ./yak gen-src gen-views start
2016-11-11T17:41:26.266Z - info: server DEFAULT listening at http://www.yaktor_test.yaktor (ip 172.18.0.5)
Matthew Adams
@matthewadams
Nov 11 2016 17:50
0.60.1 was released ~5 mins ago :)
Barrett Cervenka
@barrettc
Nov 11 2016 17:51
Just for sanity check, are you trying to go to http://www.myapp.yaktor or http://www.yaktor_test.yaktor? In your case, it would be the latter
justinr1234
@justinr1234
Nov 11 2016 17:51
latter and IP address
going to uninstall everything and restart with node 4 and see what happens
Barrett Cervenka
@barrettc
Nov 11 2016 17:51
OK
justinr1234
@justinr1234
Nov 11 2016 17:52
Does npm 3 hurt anything? (on my local machine)
Barrett Cervenka
@barrettc
Nov 11 2016 17:53
Well everything is controlled by the container - the version of node/npm you have locally really shouldn't matter. When you run yak start, were there any errors related to soctun?
Matthew Adams
@matthewadams
Nov 11 2016 17:53
If you’re using ./yak, then you only need docker to be installed. You wouldn’t be using any local npm or node version — it’s governed by our docker image.
justinr1234
@justinr1234
Nov 11 2016 18:06
So ./yak interfaces to the docker image to proxy the commands?
Or should I be running that from a bash to the docker container? ... looks like I'm already inside the container? :)
Barrett Cervenka
@barrettc
Nov 11 2016 18:09
./yak will start up the Docker containers for you with the required versions of everything. If you are having problems accessing the URL, can you make a gist with the output of everything from the ./yak start command and we can take a look?
justinr1234
@justinr1234
Nov 11 2016 18:10
I'm still rerunning, will see what happens .... Also when I started all this with node 6 as the current version on my local machine it complained about missing grunt-browserify ... redoing this with node 4.2.1 as my current version is allows the ./yak to run properly so far
Getting rid of everything and restarting with node 4.2.1 as my current version fixed all my issues
Barrett Cervenka
@barrettc
Nov 11 2016 18:12
Great, I'll talk to the other guys and see what might be getting the local and Docker versions of node confused with each other
justinr1234
@justinr1234
Nov 11 2016 22:55
Hey guys, so I changed my DNS and I'm able to get to the docs now, but it appears I'm still not able to get to the Eclipse plugin
This XML file does not appear to have any style information associated with it. The document tree is shown below.