00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:07  * ircretaryjoined
00:02:26  * YoYquit (Quit: Leaving...)
00:04:12  * YoYjoined
00:04:51  * InconceivableBjoined
00:12:49  * topwobblejoined
00:16:31  * defunctzombiechanged nick to defunctzombie_zz
00:21:00  * InconceivableBquit (Quit: Computer has gone to sleep.)
00:22:51  * Slytopic: Nodejitsu | (Support Mon-Fri 9am-8pm EST)
00:27:56  * InconceivableBjoined
00:36:00  * alxjoined
00:37:59  * bzooquit (Remote host closed the connection)
00:38:25  * bzoojoined
00:40:14  * alxquit (Ping timeout: 240 seconds)
00:42:55  * bzooquit (Ping timeout: 245 seconds)
00:43:12  * towskiquit (Remote host closed the connection)
00:44:37  * Kimmiquit (Quit: Page closed)
00:47:10  * defunctzombie_zzchanged nick to defunctzombie
00:50:38  * spopequit (Ping timeout: 240 seconds)
00:50:49  * c4miloquit (Remote host closed the connection)
00:57:35  * kwhinneryjoined
01:08:38  * Mickeyjoined
01:09:06  <Mickey>I can't seem to connect to my "Socket" using "io.connect" from my client :/
01:09:33  <Mickey>does anybody have a minute or 2? :)
01:11:12  <julianduque>Mickey: what is the problem?
01:12:11  <Mickey> var socket = io.connect('http://myapp.jit.su');
01:12:18  <Mickey>from the client is not working
01:12:58  * cc123quit (Quit: cc123)
01:13:06  <Mickey>http://piratepad.net/YseXl5p78M
01:13:10  <Mickey>my server :)
01:14:45  <julianduque>try with https://myapp.jit.su
01:16:38  * sportoquit (Ping timeout: 240 seconds)
01:18:31  <Mickey>hm, still nothing :/
01:19:10  <julianduque>do you have an error or something?
01:19:19  <julianduque>Mickey: what is your username/appname?
01:19:29  <Mickey>oandreasson
01:19:31  * sportojoined
01:19:36  <Mickey>app name is joinatapp :)
01:23:52  * cronopioquit (Ping timeout: 264 seconds)
01:25:24  * bzoojoined
01:25:30  * cronopiojoined
01:27:38  * bzooquit (Remote host closed the connection)
01:27:51  * Samuel_Roldanjoined
01:28:12  * bzoojoined
01:28:57  <Mickey>julianduque: can you find it? :)
01:29:45  <julianduque>Mickey: use this approach and let me know if it works.. https://gist.github.com/julianduque/377be3ac383d5219b8c0
01:32:20  * bzooquit (Ping timeout: 240 seconds)
01:32:50  <Mickey>ah much better :) Now the client seems to be working :) Going to test the server as well
01:32:53  <Mickey>thank you so much! :)
01:33:30  <julianduque>:)
01:36:19  <Mickey>hm, the app seemed to have crashed
01:36:30  <Mickey>I might have a loop between the client / server
01:38:48  * Nodejitsu-Githubjoined
01:38:48  <Nodejitsu-Github>[nodejitsu-api] julianduque pushed 1 new commit to master: http://git.io/d9_djg
01:38:48  <Nodejitsu-Github>nodejitsu-api/master 1060d5f Julian Duque: Merge pull request #26 from nodejitsu/preacher...
01:38:48  * Nodejitsu-Githubpart
01:39:21  * joemccannquit (Quit: joemccann)
01:40:03  <jesusabdullah>mmalecki: o/
01:40:35  * Nodejitsu-Githubjoined
01:40:35  <Nodejitsu-Github>[nodejitsu-api] julianduque pushed 1 new commit to master: http://git.io/HRT1bw
01:40:35  <Nodejitsu-Github>nodejitsu-api/master 1939009 Julian Duque: [dist] update preacher-api dep to 0.1.3
01:40:35  * Nodejitsu-Githubpart
01:41:25  * rosskquit (Remote host closed the connection)
01:42:09  <Mickey>now it seems to run fine :)
01:42:15  <Mickey>thank you again!
01:42:51  <julianduque>:)
01:43:04  * topwobblequit (Quit: topwobble)
01:44:14  * julianduquequit (Quit: leaving)
01:50:23  <jesusabdullah>oh man I *want* to accept ember.js but, man, even the fans are like, "yeah this is broken. Yeeah, that's broken too."
01:54:21  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
01:55:35  <nathan7>jesusabdullah: heh
01:55:59  <nathan7>jesusabdullah: browserland is a strange place
01:56:05  <jesusabdullah>yeah
01:56:07  <jesusabdullah>but like
01:56:10  <nathan7>jesusabdullah: I'm glad browserify is this awesome these days
01:56:24  <jesusabdullah>I can accept Angular and that's REALLY weird
01:56:28  <mmalecki>jesusabdullah: /o
01:56:31  <mmalecki>er \o
01:56:33  <jesusabdullah>sup dawg?
01:56:46  <jesusabdullah>I went to an ember.js meetup because I wanted to meet some local javascripters outside of work
01:56:50  <mmalecki>nm, doing a huge deployment, how are you?
01:56:57  <mmalecki>oh, how'd that work for you?
01:56:59  <mmalecki>did you die?
01:57:00  <jesusabdullah>These guys are alright but like
01:57:04  * ranglejoined
01:57:09  <jesusabdullah>this looks so annoying to use
01:57:53  <jesusabdullah>the only part that looks cool to me is https://github.com/emberjs/data/tree/jj-abrams
01:58:11  <jesusabdullah>which is the bleeding edge version of their ODM
01:58:29  <jesusabdullah>but the standard REST backend assumes you're running it against, like
01:58:36  <jesusabdullah>a particular subset of rails-like backends
01:58:54  <jesusabdullah>at that point I might as well write my own objects right? Am I crazy for that?
01:59:02  * julianduquejoined
01:59:09  <jesusabdullah>idk dude
01:59:21  <jesusabdullah>ember.json lolwut
01:59:32  <julianduque>?
01:59:42  <nathan7>Yeah, the ember dudes are like "we hate JS.. but we'll use it"
01:59:53  <jesusabdullah>I mean
01:59:54  <jesusabdullah>kind of?
01:59:56  <jesusabdullah>idk dude
01:59:59  * ranglequit (Client Quit)
02:00:36  <jesusabdullah>my brainwaves just don't jibe well with the ember team's
02:00:37  <nathan7>somewhere in the next week my laptop will die I think
02:00:40  <jesusabdullah>different wavelengths
02:00:43  <jesusabdullah>weak nathan7
02:00:52  <nathan7>it's an amazing source of hot air at the moment
02:00:59  <nathan7>I've had hot air stations that did worse
02:01:28  <jesusabdullah>I hate that you need to have a special build tool to use ember
02:01:30  <jesusabdullah>hate it a lot
02:01:43  * Nodejitsu-Githubjoined
02:01:43  <Nodejitsu-Github>[jitsu] julianduque pushed 2 new commits to preacher: http://git.io/bdOwmQ
02:01:43  <Nodejitsu-Github>jitsu/preacher 0d1ac25 Julian Duque: [dist] bump [email protected]
02:01:43  <Nodejitsu-Github>jitsu/preacher 55e158e Julian Duque: [fix] Back to nodejitsu-api
02:01:43  * Nodejitsu-Githubpart
02:02:26  <jesusabdullah>https://www.youtube.com/watch?v=DjydOI4MEIw
02:03:05  <julianduque>new logs are awesome <3
02:03:12  <julianduque>well, it will be awesome :p
02:03:38  * mmaleckitopic: Nodejitsu | Cloud status: scheduled maintanance in progress.
02:03:45  * travis-cijoined
02:03:45  <travis-ci>[travis-ci] nodejitsu/jitsu#470 (preacher - 55e158e : Julian Duque): The build is still failing.
02:03:45  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/14d61f41e3fd...55e158e0293b
02:03:45  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10263753
02:03:45  * travis-cipart
02:05:10  * jgablequit (Quit: Computer has gone to sleep.)
02:05:12  <jesusabdullah>good luck mmalecki !!
02:05:25  * sportoquit (Ping timeout: 245 seconds)
02:05:52  * kwhinneryquit (Quit: kwhinnery)
02:06:29  <nathan7>jesusabdullah: wtf? special build tool?
02:06:43  <jesusabdullah>nathan7: not only that but they haven't even fleshed that out yet
02:07:14  <jesusabdullah>nathan7: look at ember-tools on npm, and note that it's basically abandonware cause there's this ember-app-kit thing some people are working on
02:07:41  <jesusabdullah>nathan7: a lot of it is because they're all about precompiling handlebars templates but ember has a modified implementation even though wycats wrote both
02:08:52  <jesusabdullah>nathan7: there's a hilarious stack overflow answer by wycats where he's like, "you have to load all this crap, shim out some browser APIs, run Ember.riggledogg.sanchez(template), save it, ??!?!, good to go
02:10:00  <nathan7>jesusabdullah: heh
02:10:01  * joshsmithquit (Quit: joshsmith)
02:10:10  <nathan7>jesusabdullah: wycats is straight out bonkers, imho
02:10:17  <jesusabdullah>yeah idk
02:10:20  <jesusabdullah>I met him once, kind of
02:10:26  <jesusabdullah>I really wanted to meet Garann but he was there too
02:10:44  <jesusabdullah>he chewed out this poor junior dev from google for like 20 minutes over how much he hated the closure ecosystem
02:10:53  <jesusabdullah>like the jr dev had any choice in the matter
02:10:56  <jesusabdullah>tsk tsk
02:10:59  <nathan7>ah, you told me that one before, yeah
02:11:40  <jesusabdullah>garann's rad I'd love to hang with her again
02:12:08  <nathan7>all the rad people are at confs
02:12:16  <nathan7>and I have to be at school when all the confs happen :(
02:12:32  <nathan7>I might manage JSconEU though
02:12:35  <jesusabdullah>I'm seriously hoping I get to talk at cascadiajs
02:12:40  <jesusabdullah>really really really want to talk there
02:12:50  * joshonthewebjoined
02:13:01  <jesusabdullah>but man the competition is STEEP
02:13:22  <nathan7>jsconfeu is actually on a weekend and in Europe
02:13:32  <jesusabdullah>yeah well
02:13:48  <jesusabdullah>I'm in the rockies right now so
02:14:08  <nathan7>the closest thing to 'doable' so far was ScotlandJS, which was one day from overlapping with my school holidays
02:15:00  <jesusabdullah>I was so bummed I had to cancel scotlandjs
02:15:03  <jesusabdullah>;__;
02:16:17  <nathan7>bleh, I should sleep
02:16:21  <nathan7>quarter past 4AM
02:16:29  <nathan7>I got some gnarly source map shit working
02:16:30  <jesusabdullah>ouch
02:16:35  <jesusabdullah>word
02:16:44  <nathan7>and I'm not even gonna use it, haha
02:17:05  <nathan7>I made a browserify transform for uglify
02:17:25  <nathan7>like before bundling
02:17:33  <nathan7>so it'll cut out stray requires and stuff
02:17:49  <nathan7>(I still have to teach uglify some stuff about globals)
02:18:26  * Praimenjoined
02:19:08  <nathan7>like, if I can teach it there's no AMD define and there's always a module and exports
02:19:12  <nathan7>it'd cut out all the UMD crap
02:19:57  <nathan7>I made it compose source maps, so you can feed in your generated JS with sourcemap and get it out minified with the right sourcemap
02:20:08  <nathan7>(the source map composition of uglify is fucked up)
02:20:09  * joshsmithjoined
02:25:50  * aaronshafjoined
02:25:55  <mmalecki>jesusabdullah: thanks!
02:26:03  <mmalecki>jesusabdullah: doing our best
02:26:35  <aaronshaf>jesusabdullah: Funny to see you in here now :) We just saw each other
02:28:17  * defunctzombiechanged nick to defunctzombie_zz
02:30:53  * defunctzombie_zzchanged nick to defunctzombie
02:41:06  <Mickey>when will the cloud be back up? :)
02:41:37  * stevemanueljoined
02:45:29  * Samuel_Roldanquit (Quit: Samuel_Roldan)
02:46:34  * joshonthewebquit (Quit: Computer has gone to sleep.)
02:47:20  * sportojoined
02:49:35  <mmalecki>Mickey: we're working on it right now. should be 30 min - an hour, we're behind schedule I'm afraid
02:49:55  <Mickey>mmalecki: ok! :)
02:54:57  * thepumpkinquit (Remote host closed the connection)
02:57:12  * Samuel_Roldanjoined
03:08:49  * Nodejitsu-Githubjoined
03:08:49  <Nodejitsu-Github>[jitsu] mmalecki pushed 1 new commit to master: http://git.io/MGMVUg
03:08:49  <Nodejitsu-Github>jitsu/master d5292ed Maciej Małecki: Merge pull request #462 from nodejitsu/preacher...
03:08:49  * Nodejitsu-Githubpart
03:09:07  * tylerstalderjoined
03:10:45  * travis-cijoined
03:10:45  <travis-ci>[travis-ci] nodejitsu/jitsu#472 (master - d5292ed : Maciej Małecki): The build was broken.
03:10:45  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/6b41f255be81...d5292edcbd42
03:10:45  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10265054
03:10:45  * travis-cipart
03:12:45  * kwhinneryjoined
03:12:48  * kwhinneryquit (Client Quit)
03:13:32  * thepumpkinjoined
03:14:46  * Samuel_Roldanquit (Quit: Samuel_Roldan)
03:18:33  * Praimenquit (Quit: Page closed)
03:23:48  * xobbobjoined
03:23:53  * kenperkinsjoined
03:24:19  * joshsmithquit (Ping timeout: 246 seconds)
03:24:27  * c4milojoined
03:24:51  * kenperkinsquit (Client Quit)
03:27:59  * SomeoneWeirdquit (Quit: ZNC - http://znc.in)
03:29:05  <jesusabdullah>mmalecki: excellent news
03:31:11  <mmalecki>jesusabdullah: isn't it?
03:31:23  <mmalecki>jesusabdullah: doing the DNS switch in few minutes.
03:31:31  <mmalecki>jesusabdullah: opening the floodgates and all that
03:31:37  <mmalecki>jesusabdullah: jcrugzz already bought a boat
03:34:59  <jesusabdullah>lol fantastic
03:36:57  * defunctzombiechanged nick to defunctzombie_zz
03:39:44  * defunctzombie_zzchanged nick to defunctzombie
03:48:59  * Nodejitsu-Githubjoined
03:48:59  <Nodejitsu-Github>[nodejitsu-api] julianduque pushed 1 new commit to master: http://git.io/ArG_kg
03:48:59  <Nodejitsu-Github>nodejitsu-api/master 9d61150 Julian Duque: [dist] v0.5.1
03:48:59  * Nodejitsu-Githubpart
03:59:36  * topwobblejoined
04:03:43  * SomeoneWeirdjoined
04:04:06  * SomeoneWeirdchanged nick to Guest18265
04:05:19  * Guest18265part
04:08:54  * Tom0101joined
04:09:31  <Tom0101>what happens to my app when my subscription expires?
04:09:48  * Rob_____joined
04:13:47  * Nodejitsu-Githubjoined
04:13:47  <Nodejitsu-Github>[nodejitsu-api] mmalecki pushed 2 new commits to master: http://git.io/Q6113g
04:13:47  <Nodejitsu-Github>nodejitsu-api/master c40ab9d Maciej Małecki: [dist] Depend on `[email protected]`
04:13:47  <Nodejitsu-Github>nodejitsu-api/master c50e886 Maciej Małecki: [dist] Bump version to 0.5.2
04:13:47  * Nodejitsu-Githubpart
04:13:57  * Nodejitsu-Githubjoined
04:13:57  <Nodejitsu-Github>[nodejitsu-api] mmalecki tagged v0.5.2 at 7aef877: http://git.io/r9Uivw
04:13:57  * Nodejitsu-Githubpart
04:14:56  * joeybakerquit (Quit: Computer has gone to sleep.)
04:15:23  * Nodejitsu-Githubjoined
04:15:23  <Nodejitsu-Github>[jitsu] julianduque pushed 2 new commits to master: http://git.io/IJhpiA
04:15:23  <Nodejitsu-Github>jitsu/master 631ddb1 Julian Duque: [dist] v0.13.0
04:15:23  <Nodejitsu-Github>jitsu/master a18ea59 Julian Duque: [dist] bump [email protected]
04:15:23  * Nodejitsu-Githubpart
04:15:58  * Nodejitsu-Githubjoined
04:15:58  <Nodejitsu-Github>[jitsu] mmalecki pushed 1 new commit to master: http://git.io/j1Wgig
04:15:58  <Nodejitsu-Github>jitsu/master 63393cc Maciej Małecki: [fix] Depend on `[email protected]`
04:15:58  * Nodejitsu-Githubpart
04:16:42  * x_orjoined
04:17:08  * travis-cijoined
04:17:08  <travis-ci>[travis-ci] nodejitsu/jitsu#473 (master - a18ea59 : Julian Duque): The build was fixed.
04:17:08  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/d5292edcbd42...a18ea59e2c20
04:17:08  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10266052
04:17:08  * travis-cipart
04:17:47  * travis-cijoined
04:17:47  <travis-ci>[travis-ci] nodejitsu/jitsu#474 (master - 63393cc : Maciej Małecki): The build was fixed.
04:17:47  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/a18ea59e2c20...63393ccaf51a
04:17:47  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/10266076
04:17:47  * travis-cipart
04:19:55  * joshonthewebjoined
04:25:03  * Nodejitsu-Githubjoined
04:25:04  <Nodejitsu-Github>[jitsu] julianduque tagged v0.13.0 at master: http://git.io/_pozNA
04:25:04  * Nodejitsu-Githubpart
04:29:54  * c4miloquit (Remote host closed the connection)
04:37:28  * daviddiasquit (Remote host closed the connection)
04:38:05  * daviddiasjoined
04:42:05  * daviddiasquit (Ping timeout: 245 seconds)
04:48:45  * x_orquit (Ping timeout: 268 seconds)
04:51:53  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
04:53:06  * Samuel_Roldanjoined
04:53:34  * bzoojoined
04:55:19  <aaronshaf>Trying to pay my bill :-)
04:55:25  <aaronshaf>For the record, it's down :)
04:57:01  <mmalecki>what's down?
04:59:23  * joshonthewebquit (Quit: Computer has gone to sleep.)
05:05:22  <aaronshaf>Twitter says your done, but "We're currently undergoing maintenance. Please check #nodejitsu on irc.freenode.net for updates." is what I get upon attempting to login
05:05:29  <aaronshaf>*you're
05:06:05  * Rob_____quit (Ping timeout: 250 seconds)
05:06:11  <mmalecki>aaronshaf: oh? can I see the log? it's possible that your DNS is still propagating
05:06:21  <mmalecki>aaronshaf: we changed the DNS of the master API
05:06:31  <aaronshaf>This is on the nodejitsu web site itself
05:07:28  <mmalecki>can I see a screenshot? not sure what you're referring to
05:08:10  <aaronshaf>http://i.imgur.com/1ZLurdj.png
05:08:44  * joshonthewebjoined
05:11:34  <mmalecki>oh, yeah, looking at this right now, thanks
05:11:40  <aaronshaf>Thanks
05:12:44  * x_orjoined
05:13:32  * aaronshafquit (Remote host closed the connection)
05:17:16  * x_orquit (Ping timeout: 264 seconds)
05:17:56  * paralleljoined
05:18:06  * bzooquit (Remote host closed the connection)
05:18:43  * bzoojoined
05:23:24  * bzooquit (Ping timeout: 276 seconds)
05:26:32  * rcombsjoined
05:30:28  * mokesjoined
05:38:00  * x_orjoined
05:38:55  * st_lukejoined
05:39:40  * bzoojoined
05:47:06  <Tom0101>how do I send e-mail from nodejitsu servers?
05:48:17  <julianduque>Tom0101: you'll need to use an external smtp service
05:48:45  * andreypoppjoined
05:51:26  * x_orquit (Ping timeout: 240 seconds)
05:53:45  * sreeixjoined
05:54:23  * Samuel_Roldanquit (Quit: Samuel_Roldan)
05:54:28  * thepumpkinquit (Remote host closed the connection)
05:54:57  * thepumpkinjoined
05:55:36  * mokesquit (Remote host closed the connection)
05:56:52  * mokesjoined
05:59:47  * bzooquit (Remote host closed the connection)
05:59:48  * thepumpkinquit (Ping timeout: 276 seconds)
05:59:53  * st_lukequit (Remote host closed the connection)
06:00:23  * bzoojoined
06:00:53  * defunctzombiechanged nick to defunctzombie_zz
06:02:32  * topwobblequit (Quit: topwobble)
06:03:00  * cronopioquit (Quit: Lost terminal)
06:03:13  * miklquit (Ping timeout: 246 seconds)
06:05:13  * bzooquit (Ping timeout: 268 seconds)
06:06:08  * swaagie`sleepchanged nick to swaagie
06:06:15  * frenchtoastjoined
06:09:02  * parallelquit (Remote host closed the connection)
06:11:59  * ionellajoined
06:13:43  * frenchtoastquit (Ping timeout: 246 seconds)
06:17:21  * mokesquit (Remote host closed the connection)
06:18:54  * tylerstalderquit (Quit: Computer has gone to sleep.)
06:20:33  * mokesjoined
06:20:34  * tobiejoined
06:24:09  * andreypoppquit (Quit: andreypopp)
06:27:24  * jetiennequit (Quit: jetienne)
06:28:20  * andreypoppjoined
06:28:40  * mmaleckitopic: Nodejitsu | Cloud status: production is running new stack.
06:29:18  * julianduquequit (Quit: leaving)
06:29:26  * julianduquejoined
06:32:18  * mikl1joined
06:33:55  * ionellaquit (Remote host closed the connection)
06:39:35  * paralleljoined
06:40:46  * sreeixquit (Quit: sreeix)
06:48:09  * parallelquit (Ping timeout: 264 seconds)
06:49:15  * tobiequit (Quit: tobie)
06:54:52  * jetiennejoined
07:03:34  * ejeklintjoined
07:08:16  * tobiejoined
07:09:40  * andreypoppquit (Quit: andreypopp)
07:10:35  * mikl1quit (Ping timeout: 268 seconds)
07:11:20  * mikljoined
07:14:27  * ejeklintquit (Quit: ejeklint)
07:18:23  <Tom0101>julianduque: really? I didn't think about all these extra costs of running external services like the database, logging and now even SMTP
07:18:31  <Tom0101>so there is no way to use nodejitsu
07:18:39  <Tom0101>nodejitsu's SMTP server?
07:19:04  * spolujoined
07:19:45  <jcrugzz>Tom0101: we use sendgrid for sending emails
07:19:52  <jcrugzz>its fairly cost effective
07:20:22  <Tom0101>I will look into it
07:20:48  <Tom0101>are there any other external services that I will need for a normal app? other than databases, logging and SMTP I mean
07:21:02  <Tom0101>I guess not but I didn't think about SMTP before either
07:22:28  * defunctzombie_zzchanged nick to defunctzombie
07:23:34  <jcrugzz>Tom0101: you shouldnt have to worry about logging if you are using our service :).
07:24:12  <Tom0101>jcrugzz: how is that? I need to keep track of what's happening on production
07:24:34  <jcrugzz>wait until you see our blog post later today :)
07:24:53  <Tom0101>ah right, I heard about this before, I will wait for it ;)
07:28:01  * InconceivableBquit (Quit: Computer has gone to sleep.)
07:32:02  * ionellajoined
07:33:02  * ejeklintjoined
07:35:20  * frenchtoastjoined
07:59:54  * mokesquit (Remote host closed the connection)
08:03:28  * blevsjoined
08:09:43  * mesoquit (Read error: Connection reset by peer)
08:10:15  * mesojoined
08:11:43  * UBjoined
08:14:40  * benjaminbenbenjoined
08:14:55  * julianduquequit (Quit: leaving)
08:15:37  * sreeixjoined
08:20:02  * andreypoppjoined
08:23:15  * UBquit (Quit: Page closed)
08:29:03  * fb55joined
08:34:35  * jcrugzzquit (Ping timeout: 245 seconds)
08:44:59  * paralleljoined
08:47:31  * alxjoined
08:47:57  * fb55quit (Remote host closed the connection)
08:49:05  * ask11joined
08:52:40  * alxquit (Ping timeout: 264 seconds)
08:52:57  * coen-hydejoined
08:53:30  <Tom0101>As long as I am not having any performance issues, what does adding more drones in an individual plan give me? It still doesn't provide something like automatic failover right?
08:54:45  * sportoquit (Quit: Computer has gone to sleep.)
08:55:22  <Tom0101>(apart from running multiple applications)
08:57:28  * Mickeyquit (Quit: This computer has gone to sleep)
09:00:31  * mokesjoined
09:05:02  * parallelquit (Ping timeout: 240 seconds)
09:08:59  * mokesquit (Ping timeout: 268 seconds)
09:15:52  * benjaminbenbenquit (Quit: benjaminbenben)
09:18:06  * coen-hydequit (Quit: coen-hyde)
09:20:39  * andreypoppquit (Quit: andreypopp)
09:21:37  * sreeixquit (Quit: sreeix)
09:23:15  * Mickeyjoined
09:23:55  * ask11quit (Ping timeout: 250 seconds)
09:30:02  * blevsquit (Quit: Computer has gone to sleep.)
09:32:29  * mokesjoined
09:34:01  * fb55joined
09:37:50  * alxjoined
09:39:02  * fb55quit (Remote host closed the connection)
09:39:30  * fb55joined
09:44:03  * fb55quit (Ping timeout: 276 seconds)
09:44:19  * sportojoined
09:52:57  * mesoquit (Remote host closed the connection)
09:54:14  * xymoxquit (Ping timeout: 240 seconds)
09:54:40  * alxquit (Remote host closed the connection)
09:55:49  * benjaminbenbenjoined
09:59:03  * xymoxjoined
10:01:18  * alxjoined
10:03:51  * Tom0101quit (Remote host closed the connection)
10:11:10  * ejeklintquit (Quit: ejeklint)
10:19:10  * spoluquit (Ping timeout: 245 seconds)
10:22:18  * sreeixjoined
10:25:15  * blevsjoined
10:26:07  * ejeklintjoined
10:30:17  * mesojoined
10:30:40  * defunctzombiechanged nick to defunctzombie_zz
10:41:13  * andreypoppjoined
10:42:11  * fb55joined
10:47:46  * mokesquit (Remote host closed the connection)
10:59:15  * deric_joined
11:00:49  * BG_joined
11:02:15  <BG_>If maintenance is supposed to be done, is there a reason why I cannot log into https://www.nodejitsu.com/ ?
11:02:24  * papachanjoined
11:02:43  * paralleljoined
11:03:07  <BG_>I keep getting "We're currently undergoing maintenance. "
11:03:27  <deric_>ditto
11:03:42  <ejeklint>me too
11:04:53  * mokesjoined
11:10:10  * parallelquit (Ping timeout: 256 seconds)
11:10:33  * fb55quit (Remote host closed the connection)
11:11:03  * ionellaquit (Remote host closed the connection)
11:12:06  * ionellajoined
11:12:55  * standoojoined
11:12:56  * standooquit (Remote host closed the connection)
11:13:04  * standoojoined
11:14:10  * maximilian_joined
11:14:12  * fb55joined
11:14:12  <maximilian_>#nodejitsu
11:14:25  * andreypoppquit (Quit: andreypopp)
11:15:51  * andreypoppjoined
11:16:17  * ionellaquit (Ping timeout: 240 seconds)
11:17:06  * maximilian_quit (Client Quit)
11:18:45  * alxquit (Remote host closed the connection)
11:20:31  <`3E>BG_: That is an excellent question.
11:20:45  <ejeklint>All jitsus asleep?
11:21:05  <BG_>Seems like it.
11:21:15  <`3E>ejeklint: The people who done the migration are sleeping
11:21:16  * Mickeyquit (Quit: This computer has gone to sleep)
11:21:19  <`3E>but i'll see what I can do about it
11:21:29  <`3E>But deploy's should be online no the less
11:22:02  <ejeklint>Testing...
11:22:49  <ejeklint>Nope, get a 500. We're deploying to the Amsterdam node.
11:23:00  <BG_>Same here "Nodejitsu Error (500): Internal Server Error"
11:23:11  <ejeklint>Big demo in 38 minutes and we can't deploy.
11:24:20  <`3E>deploying to a 256mb drone does seem to work for me
11:24:29  <`3E>What kind of size drone are you guys deploying to
11:25:00  <ejeklint>No idea. :) Can't login to console either to check it.
11:25:00  <BG_>Much smaller than 256
11:25:08  * andreypoppquit (Quit: andreypopp)
11:25:22  <`3E>256 is the smallest we have BG_ :)
11:25:38  <ejeklint>Are you deploying with newest tool btw?
11:25:51  <BG_>Ok, then I have no idea what "size" means :)
11:26:22  <`3E>ejeklint: re-installing jitsu as we speak
11:26:25  <BG_>I updated jitsu 4-5 hours ago.
11:26:40  <`3E>I was running on a git branch which should be merged in to master
11:29:34  * papachanpart ("Saliendo")
11:30:08  <`3E>https://github.com/nodejitsu/nodejitsu/blob/a8b67ff04c13d96f25a2eb3bdf457215d7a65c4f/lib/nodejitsu/master/service.js#L40-L51
11:30:16  <`3E>woops wrong channel
11:30:18  <`3E>ignore me
11:32:53  * BG_quit (Quit: Page closed)
11:34:44  * kscully27joined
11:41:43  * mikl1joined
11:41:53  * sportoquit (Quit: Textual IRC Client: www.textualapp.com)
11:43:21  * ionellajoined
11:44:33  * miklquit (Ping timeout: 264 seconds)
11:45:38  * alxjoined
11:50:09  * Mickeyjoined
11:51:20  * mmaleckichanged nick to mmalecki[zzz]
11:55:19  <`3E>If you are still getting maintenance errors, now would be great time to tell us. They should all be fixed, except for our homepage, which will be fixed in 20 seconds .. starting now.
11:55:55  * donbonifacioSWATjoined
11:56:11  <ejeklint>Still can't deploy...
11:57:06  * alxquit (Remote host closed the connection)
11:57:09  <`3E>ejeklint: what is the exact output of jitsu, can you gist taht?
11:57:12  <`3E>that*
11:58:21  <ejeklint>The end of it all here: https://gist.github.com/ejeklint/6249244
11:58:49  <ejeklint>npm exits apparently
12:00:23  <`3E>Code 34, that's a new one
12:01:09  <ejeklint>Yeah, only google hit is my gist. Win!
12:02:38  * spolujoined
12:03:16  <`3E>instant indexing, that's quite nice imho
12:03:29  <`3E>Almost makes you wonder what kind of github/google integration there is..
12:03:57  <ejeklint>We are all for sale through Google, aren't we...
12:06:12  * benjaminbenbenquit (Quit: benjaminbenben)
12:07:10  <`3E>ejeklint: Anyways, we're working on resolving this
12:09:38  <ejeklint>Cool. Fingers crossed then.
12:12:32  * Ry0_joined
12:15:02  * pjjoined
12:15:26  * pjchanged nick to Guest94934
12:15:31  * rvaggquit (Quit: ta ta)
12:16:01  * Guest94934part
12:19:37  * fb55quit (Remote host closed the connection)
12:20:37  * fb55joined
12:20:55  * fb55quit (Remote host closed the connection)
12:21:50  * thealanwattsriotjoined
12:23:55  * rvaggjoined
12:24:28  * frenchtoastquit (Ping timeout: 264 seconds)
12:26:09  * kscully27quit (Read error: No route to host)
12:26:23  * kscully27joined
12:26:34  * fb55joined
12:26:42  * Mickeyquit (Quit: This computer has gone to sleep)
12:27:32  * Mickeyjoined
12:29:21  * kscully27quit (Read error: No route to host)
12:29:34  * kscully27joined
12:31:43  * Mickeyquit (Ping timeout: 246 seconds)
12:32:30  <ejeklint>Now npm exits with code 1 so at least there's variation to it.
12:32:39  <ejeklint>:)
12:32:44  * alxjoined
12:35:41  * jlankquit (Remote host closed the connection)
12:37:46  <swaagie>ejeklint: how large is the project your trying to upload? indication is fine
12:40:54  <ejeklint>swaagie: very small, less than 500 LOC
12:41:08  <swaagie>are the node_modules bundled?
12:41:59  * draftnightjoined
12:42:21  <ejeklint>swaagie: sry forgot, yes we have 3 node_modules
12:42:51  <draftnight>I just deployed and now it's saying my website is offline https://static.draftnight.com/static/css/boards.min.css?0.0.161-0
12:42:57  <swaagie>we got a hunch the failures are related to pacakge size, not sure yet though
12:43:15  <draftnight>I tried to login and it says "We're undergoing maintenance"
12:44:48  <swaagie>ejeklint: are the node_modules explicitly ignored or are they packaged along?
12:45:38  <ejeklint>Umm…. wait
12:46:37  <ejeklint>Do they get packaged along if you have a regular "dependencies"? I'm not the expert here...
12:46:48  <ejeklint>q
12:46:58  <ejeklint>wrong window :)
12:47:01  * kevino80joined
12:47:03  <`3E>draftnight: login through webops.nodejitsu.com
12:47:09  <`3E>we're still workin gon it
12:47:39  * Tom0101joined
12:48:13  <draftnight>ok, i can login & restarted the site, but it's still down: https://draftnightstatic.jit.su/static/css/boards.min.css?0.0.161-0
12:48:33  <ejeklint>swaagie: No we don't bundle any of the dependencies
12:48:38  * standooquit (Ping timeout: 240 seconds)
12:48:55  <`3E>draftnight: well it's crashing somewhere
12:49:00  <`3E>so check your logs
12:49:16  <draftnight>i did: it says Static server started at: 80
12:50:04  <draftnight>then i rolled back to the previous version to make sure - same thing, still says "Reached max retries limit"
12:50:07  <swaagie>ejeklint: which are the deps if I may ask?
12:50:39  * frenchtoastjoined
12:51:34  <ejeklint>swaagie: no secrets. :) nano, email-templates, postmark
12:52:31  * trygvehas problems deploying also. deploying to amsterdam center.
12:52:57  <trygve>Exits with 500 Internal Server Error, npm exited with code 1
12:53:04  <ejeklint>me too deploying to Amsterdam
12:53:43  * fb55quit (Remote host closed the connection)
12:55:08  <draftnight>Can anyone help? Versions that worked yesterday are not working now & my inbox is getting flooded with angry customers
12:56:03  <trygve>my deps is latest versions off all these deps: winston, convict, levelup, leveldown, express and usage.
12:56:24  <draftnight>There is no information in the logs
12:58:33  * mikl1quit (Quit: Connection reset by Peer Gynt)
12:58:38  <swaagie>draftnight: trygve ejeklint still investigating, we're getting on of our devs out of bed atm
12:58:49  <draftnight>http://i.snag.gy/nHHhs.jpg
12:59:02  * frenchtoastquit (Ping timeout: 240 seconds)
13:00:38  <ejeklint>Also: I still can't login to my account or access logs from cli
13:03:26  <swaagie>we're still actively looking for the underlying cause
13:03:29  * benjaminbenbenjoined
13:04:46  * indexzerojoined
13:06:24  <draftnight>I was able to work around the issue - this might help your devs figure out what's wrong...
13:06:34  * paralleljoined
13:06:41  <draftnight>i was serving files through node-static (which has worked for the last month)
13:07:14  <draftnight>i knew express was working on Nodejitsu because my other site was still up, so I swapped node-static out for express and it worked instantly
13:07:16  * Ry0_quit (Remote host closed the connection)
13:07:24  <swaagie>hm
13:08:09  <draftnight>still not seeing logging info, but at least the site is working
13:09:24  * igorpavlovjoined
13:09:37  <Tom0101>Maybe your package.json has not been shrinkwrapped? If node-static is somehow ninja patched (the same version) and something causes NPM to recheck the packages that'd cause trouble
13:10:18  <igorpavlov>Hi guys, on the status page it is said that everything is fine, but I cannot deploy an app. I have several accounts and apps at all of them cannot be deployed. Get 500 error.
13:10:22  <Tom0101>or actually shrinkwrapping would not help in that case either.. I meant in case your deps used a dynamic version rather than a static one for subdependencies
13:12:32  <igorpavlov>My accounts are: pavlovorg, cp
13:12:47  * jcrugzzjoined
13:14:43  <draftnight>my node-static version is "~0.7.0" and I actually left it in as a dependency, just never used it
13:17:59  * donbonifacioSWATquit (Remote host closed the connection)
13:21:10  * parallelquit (Ping timeout: 276 seconds)
13:23:02  * spoluquit (Ping timeout: 240 seconds)
13:27:17  * frenchtoastjoined
13:33:00  <igorpavlov>(Bump) Hi guys, on the status page it is said that everything is fine, but I cannot deploy an app. I have several accounts and apps at all of them cannot be deployed. Get 500 error.
13:33:43  <ejeklint>igorpavlov: you're not alone. They are working on it right now.
13:34:09  <swaagie>igorpavlov: status has just been updated, we've been busy trying to get to the root cause, sorry for the delay, it should be updated asap ofcourse
13:34:19  <igorpavlov>ah... that's fine! at least now I know it is not an issue with my app! thanks!
13:34:37  <igorpavlov>absolutely fine! thanks!
13:38:36  * `3Echanged nick to `3E|GONE
13:39:43  * kscully27quit (Remote host closed the connection)
13:39:44  * travis-cijoined
13:39:44  <travis-ci>[travis-ci] flatiron/winston#221 (master - 1c2a272 : Arnout Kazemier): The build passed.
13:39:44  <travis-ci>[travis-ci] Change view : https://github.com/flatiron/winston/compare/2c93353df7dd...1c2a2724b18f
13:39:44  <travis-ci>[travis-ci] Build details : http://travis-ci.org/flatiron/winston/builds/10278224
13:39:44  * travis-cipart
13:39:53  * sol_invictusjoined
13:42:31  * Tom0101quit (Ping timeout: 264 seconds)
13:45:59  * jgablejoined
13:47:21  * Rob_____joined
13:47:54  * bzoojoined
13:49:11  * Nevtepjoined
13:51:25  * kscully27joined
13:51:50  * bzooquit (Ping timeout: 240 seconds)
13:52:10  * Slaytorsonjoined
13:52:50  * kscully27quit (Remote host closed the connection)
13:54:05  * Samuel_Roldanjoined
13:54:27  * igorpavlovquit (Quit: Page closed)
14:00:54  * blevsquit (Quit: Computer has gone to sleep.)
14:04:34  * `3E|GONEchanged nick to `3rdEden
14:10:21  * sol_invictusquit (Remote host closed the connection)
14:10:40  * ionellaquit (Remote host closed the connection)
14:11:30  * frenchtoastquit (Ping timeout: 256 seconds)
14:14:08  <Nevtep>Morning I'm having problems with deploy
14:14:31  <Nevtep>error: Error running command deploy error: Nodejitsu Error (500): Internal Server Error error: npm exited with code 1
14:15:05  <Nevtep>gist: https://gist.github.com/Nevtep/32503458bea03d8b5b9d
14:15:14  <Nevtep>that's the only info I'm getting
14:15:26  <Nevtep>any ideas where to look at?
14:16:10  * blevsjoined
14:17:47  * bzoojoined
14:18:00  * Samuel_Roldanquit (Remote host closed the connection)
14:18:01  <jcrugzz>Nevtep: we are looking into it :). its a problem compiling binary modules currently
14:18:15  * rosskjoined
14:18:19  * Samuel_Roldanjoined
14:19:02  <jcrugzz>Nevtep: but if you could run a `jitsu deploy --debug` and gist the full output that would be helpful! :D
14:19:18  <Nevtep>would do that
14:19:34  <Nevtep>I believe I have some bad configurations on my package.json
14:19:41  * thepumpkinjoined
14:19:44  <Nevtep>getting packages rfom github directly
14:19:52  * Samuel_Roldanquit (Read error: Connection reset by peer)
14:20:05  <Nevtep>I¡ll get back with --debug
14:20:24  * Samuel_Roldanjoined
14:22:24  * japanajamajoined
14:23:34  * sreeixquit (Quit: sreeix)
14:25:39  <Nevtep>I use bcrypt so I guess that's that
14:37:29  * frenchtoastjoined
14:39:37  * igorpavlovjoined
14:41:28  * julianduquejoined
14:44:46  * kscully27joined
14:45:16  <Nevtep>@jcrugzz any news?
14:45:21  <Nevtep>here's debug: https://gist.github.com/Nevtep/36dbd8649755961f5bb7
14:46:55  <igorpavlov>guys, status says everything is working, but... still cannot deploy
14:47:08  <igorpavlov>Nevtep, yeah, same thing
14:47:59  * kevino80quit (Remote host closed the connection)
14:49:15  * drgerdjoined
14:49:26  * kevino80joined
14:50:44  * c4milojoined
14:53:00  <Nevtep>I'm also getting an Error:listen EINVAL from my logger
14:54:07  <swaagie>:s
14:54:13  <swaagie>status seems mangled
14:56:23  <jcrugzz>Nevtep: working through issues regarding binary modules still, thanks for all your patience :)
14:57:23  * brandonrvaughanjoined
14:59:21  <brandonrvaughan>any status on when we can log back in to admin. My site is still down.
15:01:15  <jcrugzz>brandonrvaughan: have you tried a redeploy? run a `jitsu deploy --debug` and paste the gist if it fails :). We are just having some issues with binary addons that are currently being resolved
15:01:31  <brandonrvaughan>will do thanks
15:02:21  * igorpavlovquit (Ping timeout: 250 seconds)
15:04:15  * alxquit (Remote host closed the connection)
15:05:23  <brandonrvaughan>the deploy looks like it works but I'm getting 502 Reached max retries limit
15:05:53  <brandonrvaughan>it didn't set the latest deploy to active
15:08:28  * yawntdroidjoined
15:09:33  * mdedetrichquit (Quit: Computer has gone to sleep.)
15:09:43  <jcrugzz>braondonrvaughan: username/appname?
15:09:53  * alxjoined
15:10:09  * japanajamaquit (Ping timeout: 250 seconds)
15:10:56  <brandonrvaughan>nvite.com nvite-govfest
15:11:45  * bobbycodjoined
15:13:01  <jcrugzz>brandonrvaughan: also update your jitsu with `npm install jitsu -g` and see if you can grab some logs while i look at the server
15:13:14  <brandonrvaughan>great thanks
15:14:57  * thepumpkinquit (Remote host closed the connection)
15:15:34  <brandonrvaughan>No logs for nvite-govfest in specified timespan
15:16:18  <jcrugzz>ok
15:17:39  * paralleljoined
15:18:56  * blevsquit (Quit: Computer has gone to sleep.)
15:21:19  <Nevtep>@jcrugzz I'm having the same issues that brandonrvaughan
15:21:27  * ionellajoined
15:21:32  <jcrugzz>Nevtep: it succeeds but gives a 502?
15:21:36  <Nevtep>deploy worked
15:21:42  <Nevtep>and now I get 502
15:21:54  <Nevtep>my logger is telling me this:
15:22:45  <Nevtep>https://gist.github.com/Nevtep/4686ac60b2daae95a70e
15:22:57  <Nevtep>basically Error:listen EINVAL
15:23:13  <Nevtep>using port 3000
15:24:02  <julianduque>Nevtep: what is your username/appname?
15:24:11  <trygve>deploy to amsterdam worked here now
15:24:20  <Nevtep>realfilling/FarmSharesStaging
15:24:50  <jcrugzz>Nevtep looking into it
15:25:00  * kscully27quit (Remote host closed the connection)
15:25:40  * parallelquit (Ping timeout: 246 seconds)
15:26:23  * ionellaquit (Ping timeout: 268 seconds)
15:26:24  <Nevtep>@jcrugzz thanks! updated gist with port 80 output: https://gist.github.com/Nevtep/4686ac60b2daae95a70e
15:30:24  <jcrugzz>Nevtep: very odd, i would keep it at 3000 thoug. there is some odd issue going on
15:31:03  <jcrugzz>can you guys all try redeploying and check your logs?
15:31:37  <brandonrvaughan>yeah
15:32:02  <jcrugzz>brandonrvaughan: you can even try out the `jitsu logs tail` ;)
15:32:15  <brandonrvaughan>after deploy
15:32:32  * alxquit (Ping timeout: 256 seconds)
15:32:39  <brandonrvaughan>deploying now
15:32:41  * drgerdquit (Ping timeout: 250 seconds)
15:32:54  <jcrugzz>ok cool :)
15:33:10  * trygvedeployed fine
15:33:27  <jcrugzz>trygve: whats your username/appname?
15:33:35  <jcrugzz>if its still 502
15:33:54  <trygve>chargelizer-media / Ladestasjoner
15:34:00  * arnaldocapojoined
15:34:07  <trygve>that is appname / username
15:34:34  <arnaldocapo>people that uses nodejitsu and are in this channel. are cool people!
15:34:43  * alxjoined
15:35:35  <brandonrvaughan>Express server listening on port 80
15:35:35  <brandonrvaughan>warn: error raised: Error: listen EINVAL
15:36:44  <ejeklint>Whohoo! Now I could deploy again.
15:37:54  <jcrugzz>brandonrvaughan: you see it in the logs?
15:38:08  <brandonrvaughan>yeah in the logs tails after it deployed
15:38:20  <jcrugzz>braondonrvaughan: ok
15:38:46  <Nevtep>same here
15:38:49  <Nevtep>Error:listen EINVAL
15:38:55  <Nevtep>port 300
15:38:58  <Nevtep>3000 * sry
15:39:09  * joeybakerjoined
15:39:58  <Nevtep>@jcrugzz I don't see it in jitsu logs tail though
15:40:25  <Nevtep>I have a logger handling global errors and get an email for that after deploy
15:40:29  * daviddiasjoined
15:40:45  <jcrugzz>Nevtep: ok thanks
15:41:09  * daviddia_joined
15:41:11  * alx__joined
15:41:16  * Ry0_joined
15:41:40  * paralleljoined
15:42:13  * InconceivableBjoined
15:42:14  * alxquit (Read error: Connection reset by peer)
15:42:30  * mmalecki[zzz]changed nick to mmalecki
15:42:41  * rosskquit (Remote host closed the connection)
15:43:11  * arnaldocapoquit (Read error: Connection reset by peer)
15:43:31  * arnaldocapojoined
15:45:12  * daviddiasquit (Ping timeout: 260 seconds)
15:45:54  * katowulfjoined
15:47:31  * Ry0_quit (Remote host closed the connection)
15:47:38  <katowulf>Good morning! s/morning/(afternoon|evening)/g
15:49:36  <Sly>katowulf: ohai. :)
15:50:00  * cronopiojoined
15:50:09  * arnaldocapoquit (Ping timeout: 256 seconds)
15:51:13  * Ry0_joined
15:51:26  * thepumpkinjoined
15:54:01  * rosskjoined
15:55:59  * Ry0_quit (Ping timeout: 268 seconds)
15:57:35  <katowulf>Hey gents, I can't seem to get at my logs. I have a script that is working locally but not after deploy. "We're currently undergoing maintenance. Please check #nodejitsu on irc.freenode.net for updates."
15:57:53  <nathan7>Hey katowulf
15:58:06  <nathan7>katowulf: a moment
15:58:32  <katowulf>no worries, is it valid maintenance? timeframe?
15:58:46  <katowulf>I can wait a bit; it's ancilliary--non critical script
15:58:52  * rosskquit (Remote host closed the connection)
15:59:12  * deric_quit (Quit: deric_)
15:59:21  <nathan7>We've upgraded our stack and working out a few kinks
15:59:27  * rosskjoined
15:59:49  <katowulf>ko, ty
16:00:03  <nathan7>katowulf: You might be hitting the old API server, which is disabled
16:00:11  <nathan7>In that case it's just DNS propagation
16:00:15  <katowulf>ko
16:00:19  <katowulf>is there another way to hit the logs?
16:00:36  <katowulf>I looked over the jitsu API and didn't spot anything
16:00:38  * rosskquit (Read error: Connection reset by peer)
16:01:02  * rosskjoined
16:01:17  <nathan7>katowulf: you can try jitsu set remoteHost 72.2.115.6
16:01:25  <katowulf>oh no I'm blind
16:01:31  <katowulf>ko
16:01:32  <mmalecki>nah nathan7, won't work due to reasons
16:01:49  <mmalecki>it'll still try api.nodejitsu.com because it hits /endpoints
16:01:50  <katowulf>I see the jitsu command for logs
16:01:55  <katowulf>I'll use that for now
16:02:07  <julianduque>katowulf: try with the new `jitsu logs tail` :)
16:02:15  <mmalecki>DNS should be resolving correctly soon tho
16:02:16  <nathan7>mmalecki: damnit
16:03:04  <katowulf>@julia ty!
16:03:28  <katowulf>@julian ty! : )
16:03:39  <nathan7>Did julianduque get a sex change we weren't notified about?
16:03:41  <katowulf>(what, it's just an "n")
16:04:14  <katowulf>Probably one he wasn't notified about, either
16:04:50  <julianduque>what!
16:05:01  <julianduque>:p
16:05:04  <julianduque>katowulf: no prob ;)
16:06:03  * Rob_____quit (Ping timeout: 250 seconds)
16:07:25  <Nevtep>is it working now?
16:09:28  <katowulf>@Nevtep if that was to me, no
16:09:45  <katowulf>let me try flushing dns?
16:09:52  * TooTallNatejoined
16:10:23  <katowulf>brb
16:11:23  * katowulf_joined
16:11:46  <katowulf_>still no joy here on login
16:12:55  <jcrugzz>katowulf_: what does host api.nodejitsu.com tell you?
16:13:09  <jcrugzz>and make sure you jitsu config set remoteHost api.nodejitsu.com
16:13:15  <katowulf_>nslookup: https://gist.github.com/katowulf/e9bf4ef590ced6f79a82
16:13:30  <katowulf_>{"message":"No resource specified"}
16:13:34  <jcrugzz>do api.nodejtsu.com
16:13:39  <jcrugzz>not nodejitsu.com
16:14:00  <katowulf_>Address: 72.2.115.6
16:14:04  <brandonrvaughan>i tried deploying again but same error
16:14:40  <jcrugzz>brandonrvaughan: what node are you running locally?
16:14:40  <katowulf_>also can't access logs via jitsu, is this related or because I use a CNAME? https://gist.github.com/katowulf/778f1b33620b79f30130
16:14:40  * indexzeroquit (Quit: indexzero)
16:14:43  * katowulfquit (Ping timeout: 250 seconds)
16:14:55  * katowulf_changed nick to katowulf
16:15:05  <brandonrvaughan>0.8.23
16:15:17  * parallelquit (Remote host closed the connection)
16:15:18  * bobbybuilderjoined
16:15:40  <jcrugzz>brandonrvaughan: change your engines.node in your package.json to 0.8.x
16:15:54  * paralleljoined
16:16:15  <jcrugzz>some of your modules might be broken in 0.10.x depending on how your dependencies are locked down
16:16:20  <bobbybuilder>i'm having trouble logging into webops?
16:16:26  <jcrugzz>or make sure it works locally with a fresh npm install on 0.10.x
16:16:40  <Nevtep>@jcrugzz I'm now getting an Error:Unexpected token . SyntaxError on require("./controllers/admin")
16:16:42  <brandonrvaughan>k redeploying
16:17:01  <Nevtep>is the "./" sintax wrong for accesing current dir folders?
16:17:26  <bobbybuilder>also i just deployed an update to my app and i get a 502 error when going to the webpage, but no errors from the cli
16:17:43  * mokesquit (Remote host closed the connection)
16:17:59  <nathan7>Nevtep: That should be fine
16:18:01  <brandonrvaughan>u mean switch to 0.10.x
16:18:08  <brandonrvaughan>and then npm install
16:18:13  <nathan7>Nevtep: Maybe you're not closing a string somewhere higher up, because strings aren't parsed by the JS parser
16:18:36  <jcrugzz>brandonrvaughan: yea ensure that all works locally on 0.10.x with a fresh npm install
16:18:52  <jcrugzz>cause your engine is set to >= 0.8.0 so it may be failing on 0.10.x
16:18:57  <brandonrvaughan>ok any particular 0.10 version
16:19:16  <jcrugzz>the latest is 0.10.15. when you set your package.json though, you want it to be 0.10.x
16:19:17  * alx__quit (Read error: No route to host)
16:19:24  <brandonrvaughan>great
16:19:38  * alxjoined
16:20:33  * parallelquit (Ping timeout: 276 seconds)
16:21:00  * arnaldocapojoined
16:21:06  <brandonrvaughan>doesn't look like the change to 0.8.x helped
16:21:08  * jetiennequit (Quit: jetienne)
16:21:09  <julianduque>katowulf: can you do `jitsu logs tail --debug` and share with me the output please
16:22:15  <julianduque>katowulf: also execute `npm cache clean` and then `npm install jitsu -g` please
16:22:25  <julianduque>katowulf: before the `jitsu logs tail --debug`
16:22:53  <jcrugzz>brandonrvaughan: it could have to do with your * dependencies. something may have changed in those modules that broke
16:23:21  <Nevtep>@jcrugzz unfourtunatly that's not the case :(
16:23:25  <brandonrvaughan>ok so i updated to 10.15 deleted node_modules and nom installing
16:23:42  <brandonrvaughan>so will test after that and try redeploying
16:23:43  <jcrugzz>Nevtep: yea not sure what yours might be yet, we are digging into it :)
16:23:50  <Nevtep>Ok need to tnd to some other stuff
16:23:53  <Nevtep>I'll chekc in later
16:23:59  <Nevtep>thank's!
16:24:12  * yawntdroidquit (Quit: AndroIRC - Android IRC Client ( http://www.androirc.com ))
16:25:59  * jetiennejoined
16:26:00  * pjjoined
16:26:24  * pjchanged nick to Guest88613
16:27:41  <Guest88613>Nodejitsu status page says all is now OK, but still getting maintenance messages... is everything supposed to be working now?
16:29:26  <nathan7>Guest88613: You might still be hitting the old API server
16:29:30  <nathan7>Guest88613: DNS is still propagating
16:30:03  <Guest88613>K -- thanks (Y)
16:31:24  * rosskquit (Remote host closed the connection)
16:31:47  * sol_invictusjoined
16:31:58  * rosskjoined
16:32:15  * rosskquit (Read error: Connection reset by peer)
16:32:37  * frenchtoastquit (Ping timeout: 248 seconds)
16:32:38  * rosskjoined
16:36:09  * Guest88613part
16:36:21  * sreeixjoined
16:36:56  * Flyersjoined
16:37:50  <brandonrvaughan>ok so everything works locally on 10.15
16:37:57  <brandonrvaughan>im redeploying
16:38:12  * paralleljoined
16:38:36  * Martin8900joined
16:39:43  * julianduquetopic: Nodejitsu | Cloud Status: Production is running new stack | https://blog.nodejitsu.com/major-new-features | Support hours Mon-Fri 9am to 8pm EST
16:40:05  <joeybaker>hello, I just upgraded to node 0.10 and am no getting a browser warning "no data received" when visiting my app. Does this related to the DNS propagation or should I be more worred?
16:40:30  <nathan7>joeybaker: username/appname?
16:41:09  <joeybaker>nathan7: ubntjoey/ubnt-jobs
16:42:53  * Martin8900quit (Ping timeout: 250 seconds)
16:43:35  <brandonrvaughan>after deploy ( in logs tail) Express server listening on port 80, [08/16 12:42:35 EDT][out] info: socket.io started, [08/16 12:42:35 EDT][out] warn: error raised: Error: listen EINVAL
16:43:40  * rosskquit (Remote host closed the connection)
16:44:16  * rosskjoined
16:44:25  <nathan7>investigating
16:45:09  <joeybaker>nathan7: thanks
16:45:29  * andreypoppjoined
16:47:54  * TooTallNatequit (Quit: Computer has gone to sleep.)
16:47:54  * sol_invictusquit (Remote host closed the connection)
16:48:20  * mokesjoined
16:48:29  * kevino80quit (Remote host closed the connection)
16:48:56  * kscully27joined
16:49:05  * alxquit (Remote host closed the connection)
16:49:06  * rosskquit (Ping timeout: 264 seconds)
16:49:12  <brandonrvaughan>is there no way to load the previous working version prior to this mornings deploy at least until this is resolved
16:49:55  * stevemanueljoined
16:51:21  * stevemanuelquit (Client Quit)
16:51:31  * parallelquit (Remote host closed the connection)
16:51:57  <bobbybuilder>hi i can't log into nodejitsu.com i get a message that its because of maintenance, but #nodejitsu says you finished maintenance? any ideas?
16:52:24  * Des_joined
16:52:40  <jcrugzz>bobbybuilder: dns propagation. it takes a bit to invalidate all the caches
16:52:54  <jcrugzz>make sure you clear your browser cache
16:53:10  <Flyers>someone know aproximately when the back-end will be accessible ?
16:54:16  * paralleljoined
16:54:31  * sol_invictusjoined
16:54:34  <jcrugzz>brandonrvaughan: not currently, ensure you are trying not to listen on 2 ports with both express and socket.io
16:54:48  <brandonrvaughan>no I'm not
16:54:53  <jcrugzz>cause i think socket.io lets you do something weird
16:54:58  <brandonrvaughan>this has been working already
16:55:13  <brandonrvaughan>everything has been fine up to last night
16:55:38  <brandonrvaughan>its works great locally
16:56:09  <jcrugzz>we just deployed a whole new infrastructure last night, i apologize for any inconvenience. There are a few odd things we are trying to figure out
16:56:12  <brandonrvaughan>and we didn't have issues on nodejitsu prior to my deploy this morning
16:56:27  <jcrugzz>im just trying to eliminate all possibilities
16:56:33  <jcrugzz>dont mean to offend :)
16:56:39  <brandonrvaughan>yeah none taken
16:56:49  <jcrugzz>and you must be working with my roommate evan
16:56:50  <brandonrvaughan>I'm just trying to help also
16:56:55  * mokesquit (Ping timeout: 264 seconds)
16:56:56  <brandonrvaughan>oh nice!
16:57:05  <bobbybuilder>@jcrugzz I did clear my browser cache, but i'll give it another go in a little bit
16:57:17  <katowulf>@julianduque same result after cache clean / install jitsu -g https://gist.github.com/katowulf/778f1b33620b79f30130
16:57:18  <brandonrvaughan>yeah I was just joking that i was waiting to get in contact with u
16:57:33  <brandonrvaughan>didn't know the man behind the mask
16:57:40  <jcrugzz>haha
16:57:52  <julianduque>katowulf: `jitsu logs tail --debug` please :)
16:57:53  <jcrugzz>yea i gotta dig into a few things here, but working as fast as i can
16:58:02  <katowulf>sorry, sent wrong link...
16:58:20  <brandonrvaughan>k
16:58:44  <katowulf>https://gist.github.com/katowulf/6779c0fed77d381bc3a6
17:01:13  <brandonrvaughan>i am passing process.env.PORT for socket.io
17:01:17  * ejeklintquit (Quit: ejeklint)
17:01:20  <brandonrvaughan>i assume that is still working
17:01:21  <julianduque>katowulf: let me check
17:03:15  <jcrugzz>brandonrvaughan: can you actually try updating your PORT to something thats not 80?
17:03:33  * TooTallNatejoined
17:03:33  <bobbybuilder>Also (besides not being able to log in) i just redeployed my app and when I go my site i get a 502 'reached max retries limit' error message
17:04:13  <brandonrvaughan>via jitsu env set
17:04:18  * fb55joined
17:04:32  * benjaminbenbenquit (Quit: benjaminbenben)
17:07:24  <julianduque>katowulf: found the issue, fixing it :D
17:07:56  <brandonrvaughan>i set to 3000
17:07:58  <brandonrvaughan>now what
17:08:25  <katowulf>yay! my job here is done; signing off (Katowulf: QA tester, tech supporter, entreprenuer, and most importantly, HUMBLE developer!)
17:09:12  <julianduque>:)
17:09:21  <katowulf>related to my use of CNAMEs?
17:09:47  <katowulf>(in place of jitsu urls)
17:10:29  <julianduque>katowulf: something on our new logging system, still on beta :)
17:10:41  <katowulf>ko
17:11:00  * tylerstalderjoined
17:13:13  * rosskjoined
17:13:16  * NotCoffeeTablejoined
17:13:22  * ejeklintjoined
17:13:29  * alx__joined
17:13:54  * coen-hydejoined
17:14:08  <NotCoffeeTable>Any idea when new account creation will be backup?
17:14:14  * mokesjoined
17:14:30  <jcrugzz>brandonrvaughan: try and redeploy
17:14:52  <julianduque>katowulf: can you try again?
17:14:52  <jcrugzz>sry juggling a couple different things
17:15:38  <brandonrvaughan>no worries
17:17:27  <bobbybuilder>any help for me?
17:18:20  * c4miloquit (Remote host closed the connection)
17:18:23  <jcrugzz>bobbybuilder: check your logs if you could and gist us some output, we are trying to figure everything out :)
17:18:34  <brandonrvaughan>holy crap that worked
17:19:01  <jcrugzz>brandonrvaughan: awesome, we found the bug :)
17:19:11  <Nevtep>ok back
17:19:12  <jcrugzz>slick site btw
17:19:20  <brandonrvaughan>thanks!!
17:19:33  <Nevtep>@jcrgzz I'm hitting npm 1 again :(
17:19:33  <brandonrvaughan>cool so keep port at 3000
17:20:27  <jcrugzz>brandonrvaughan: yea it doesnt like you listening on 80, we just need to fix our autocorrection on that
17:21:05  * alx__quit (Remote host closed the connection)
17:21:13  <brandonrvaughan>sounds good to me. Thanks for sticking with it and praying for u guys as u resolve these things. Great service!!
17:21:32  * jgablequit (Quit: Computer has gone to sleep.)
17:21:48  <jcrugzz>branonrvaughan: thanks :). we appreciate the kind words!
17:22:02  <jcrugzz>Nevtap: i will check out the build server
17:22:04  * jmar777joined
17:22:31  <brandonrvaughan>make sure and have evan buy u a beer for me ;) have him put it on my tab
17:23:09  <jcrugzz>brandonrvaughan: haha will do :). have a good one man
17:23:12  * Des_quit (Remote host closed the connection)
17:23:19  * brandonrvaughanquit (Quit: brandonrvaughan)
17:23:47  * xobbobquit (Quit: xobbob)
17:24:04  <jcrugzz>nevtap: remind me your username/appname?
17:24:08  <jcrugzz>Nevtap: ^
17:24:15  <Nevtep>sure
17:24:28  <Nevtep>realfilling/FarmSharesStaging
17:24:48  <jcrugzz>thanks let me check it out
17:24:59  <Nevtep>:) still hitting that SyntaxError: Unexpected token . thing I believe
17:25:11  <Nevtep>but haven't changed anything there
17:25:25  * nathan7looks
17:25:30  * julianduquequit (Quit: leaving)
17:26:10  <nathan7>Nevtep: Mind gisting the full error?
17:26:26  * jmar777quit (Remote host closed the connection)
17:27:04  * fb55quit (Remote host closed the connection)
17:27:18  * jmar777joined
17:27:24  <nathan7>hey jmar777
17:28:08  <katowulf>@julianduque interestingly, I got both the logs and an error this time: https://gist.github.com/katowulf/7a7bb94af3660311d7f2
17:28:10  * jmar777quit (Remote host closed the connection)
17:30:50  <joeybaker>nathan7: some further data points for you: I'm using bcrypt which compiles specific to the node version (I'm running the 0.10.15 in both dev and production). Also, the logs show no errors or really anything aside from my app init messages.
17:31:00  <nathan7>joeybaker: mhm
17:32:09  <Nevtep>ok on to that
17:32:16  * sreeixquit (Quit: sreeix)
17:32:36  * wsirc_2575joined
17:33:10  <wsirc_2575>hello
17:33:11  * andreypoppquit (Quit: andreypopp)
17:33:28  <katowulf>nathan7: will Julian be coming back?
17:33:41  <katowulf>can I shoot him an email with my response? He'll probably want to see it
17:34:19  <Nevtep>nathan7 I've sent you the gist
17:34:20  <nathan7>katowulf: Julian is off to university atm
17:34:32  <katowulf>(and my short term memory is very similar to no-term memory)
17:34:43  <nathan7>hehe
17:35:11  <jesusabdullah>what about mmalecki?
17:35:11  <nathan7>katowulf: [email protected] should reach him [=
17:35:18  <katowulf>ko - ty!
17:35:23  <nathan7>joeybaker: hmm? mmalecki is right here
17:35:28  <nathan7>err, jesusabdullah*
17:35:28  <jesusabdullah>well good!
17:36:15  <Nevtep>@nathan7 here is my gist: https://gist.github.com/Nevtep/5cbda1a07c7cf55b843e
17:36:30  <nathan7>Nevtep: Yar, got it
17:37:22  * bobbycodquit (Quit: Page closed)
17:37:49  * wsirc_2575quit (Ping timeout: 256 seconds)
17:37:50  * georgeredingerjoined
17:37:57  <joeybaker>nathan7: okay. sure, I though you had said you were investigating the lack of connectivity to ubntjoey/ubnt-jobs ?
17:38:03  <nathan7>joeybaker: yep
17:38:43  <joeybaker>nathan7: cool, thanks, do we need mmalecki? /confused
17:38:49  * NotCoffeeTablequit (Quit: Page closed)
17:38:55  <nathan7>joeybaker: that was a mis-tab, sorry
17:38:55  * andreypoppjoined
17:39:11  <joeybaker>nathan7: :)
17:41:45  * parallelquit (Remote host closed the connection)
17:42:28  * aheckmannjoined
17:43:08  <bobbybuilder>here is output when i 'jitsu deploy --debug' https://gist.github.com/anonymous/6251915
17:45:45  <bobbybuilder>also my latest deploy now isn't returning anything when i check it via browser
17:45:58  * joemccannjoined
17:46:49  * kscully27quit (Remote host closed the connection)
17:47:06  <nathan7>mhm
17:47:13  <jcrugzz>bobbybuilder: can you change your NODE_ENV to production and run a jitsu start?
17:47:58  * Flyersquit (Remote host closed the connection)
17:53:00  <nathan7>joeybaker: jitsu env set PORT 3000
17:53:05  <nathan7>joeybaker: that should fix it right up
17:53:55  * joshsmithjoined
17:54:09  <nathan7>seems set [=
17:54:15  <bobbybuilder>@jcrugzz: no, i'm trying to deploy my dev app, to dev site, and everything is connected to NODE_ENV so it would effect my live site (which is working fine right now)
17:54:41  <joeybaker>nathan7: perfect! followed by a jitsu apps start everything is golden – thanks!
17:55:17  <joeybaker>nathan7: 2 questions: any reason why `jistu apps restart didn't work?
17:55:30  <nathan7>joeybaker: restart doesn't reprovision etc
17:55:39  <nathan7>joeybaker: it just restarts your app, nothing more
17:55:42  <nathan7>joeybaker: start is a fresh start
17:55:43  <joeybaker>nathan7: also, what lesson should I take from this for new apps in the future
17:55:51  <nathan7>joeybaker: You just helped us find a bug
17:55:51  <joeybaker>ah, makes sense, thanks.
17:55:59  <nathan7>joeybaker: We're not handling the .listen(0) case
17:56:14  <joeybaker>cool! as long as I'm not the one Doing it Wrong™ :)
17:56:20  <joeybaker>thanks for you help!
18:00:14  * ionellajoined
18:00:27  * indexzerojoined
18:01:30  <joeybaker>nathan7: I spoke too soon, Looks like the app is now crashing after accessing it once – nothing in the logs though
18:01:37  <nathan7>joeybaker: o:
18:01:57  <jcrugzz>bobbybuilder: can you try and redeploy for me?
18:02:03  <joeybaker>sure thing
18:02:15  <joeybaker>*whoops not me
18:03:14  * paralleljoined
18:03:17  <bobbybuilder>@jcrugzz sure
18:03:51  * defunctzombie_zzchanged nick to defunctzombie
18:06:07  * cxjoined
18:06:41  <cx>servers still down?
18:07:02  * cc123joined
18:07:19  <jcrugzz>cx: shouldnt be
18:07:32  <cx>i can't log in
18:07:40  <cc123>@jcrugzz, i keep getting 502 error on our app
18:07:43  <cc123>I've tried redeploying
18:07:46  <cx>from the website.. and it gives me a server maintenance message
18:07:50  <cc123>this happened after i downsized the drones
18:08:00  <cc123>I've redeployed and restarted a few times
18:08:01  <cc123>nothing
18:08:01  <jcrugzz>cx: shift refresh the page multiple times.
18:08:04  <cc123>app.pushpinplanner.com
18:08:06  * caseywebdevjoined
18:08:07  <jcrugzz>the api is cached
18:08:14  <cc123>account projectricochet
18:08:19  <cc123>app prod-pushpin
18:08:27  <jcrugzz>bobbybuilder: make sure you are listening on a port
18:08:33  <jcrugzz>in your app
18:08:42  <jcrugzz>cc123: ill see what could be going on
18:09:15  <cx>jcrugzz: still the same... can't log in, and i get "We're currently undergoing maintenance. Please check #nodejitsu on irc.freenode.net for updates."
18:09:34  * fb55joined
18:09:49  <Sly>cx: there were some DNS changes, so your DNS may not have the new API server IP yet.
18:09:50  <jcrugzz>cx: DNS may not have propagated yet. its very dependent on the DNS servers of your internet provider and where you are located
18:10:11  <cx>ahh
18:10:54  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:10:59  <cx>in that case, i'll check back tomorrow
18:11:00  <cx>thanks
18:11:08  * cxquit (Quit: Page closed)
18:12:52  <cc123>jcrugzz: any news?
18:12:56  <cc123>i have to tell everyone what's going on
18:14:13  * cronopioquit (Read error: Connection reset by peer)
18:14:41  <jcrugzz>cc123: looking into it. But there may be a minor bug with our new setup, not sure exactly what yet. try runnng a jitsu destroy && jitsu deploy
18:15:24  <nathan7>joeybaker: Seems the port isn't getting through now
18:15:32  <coen-hyde>same, having issues
18:16:05  <coen-hyde>it looks like the port env isn't being sent to the app
18:16:26  * sol_invictusquit (Remote host closed the connection)
18:16:29  <coen-hyde>i've tried setting the PORT env manually
18:16:38  * andreypoppquit (Quit: andreypopp)
18:16:59  * sol_invictusjoined
18:17:09  <joeybaker>nathan7: odd, the code is already using process.env.PORT as the listen port, and my startup logging shows that it's listening on 3000.
18:17:39  <nathan7>joeybaker: mhm
18:18:05  <joeybaker>nathan7: it's good for one visit, then dies
18:18:12  <caseywebdev>I'm getting Error: listen EINVAL while listening on 80
18:19:08  <nathan7>caseywebdev: Use a different port, doesn't matter which
18:19:11  <nathan7>caseywebdev: anything over 1024
18:19:54  * indexzeroquit (Quit: indexzero)
18:21:22  * kscully27joined
18:21:40  * joshonthewebjoined
18:22:01  <caseywebdev>nathan7: thanks, seems to be working now
18:22:05  <caseywebdev>probably want to update https://www.nodejitsu.com/documentation/faq/#how-do-i-choose-what-port-to-use-in-nodejitsu
18:22:06  * mesoquit (Read error: Connection reset by peer)
18:22:37  * mesojoined
18:23:24  * diogogmtjoined
18:23:58  <nathan7>caseywebdev: We're resolving this issue
18:24:02  * ejeklintquit (Quit: ejeklint)
18:24:33  <caseywebdev>the issue of listening on 80 being broken or misleading docs?
18:24:46  <nathan7>ports <1024 being broken
18:24:50  <caseywebdev>alright, thakns
18:24:52  <caseywebdev>thanks*
18:24:55  <nathan7>It's behaviour we didn't port over from our old stack yet
18:25:00  <caseywebdev>gotcha
18:25:24  * caseywebdevquit (Remote host closed the connection)
18:25:31  * spopejoined
18:27:25  <coen-hyde>ok my app seems to be staying up now. I've set the PORT env and hardcoded in the app to port 3000
18:27:38  <coen-hyde>but I'm not getting fresh logs
18:28:38  <joeybaker>nathan7: I just did another deeply and everything now seems happy
18:28:51  * dbisognojoined
18:28:54  <nathan7>joeybaker: Awesome
18:29:01  <joeybaker>nathan7: thanks!
18:29:07  <nathan7>joeybaker: Looks fine on this end too [=
18:29:09  <dbisogno>When will new account registration be back up?
18:29:23  <nathan7>dbisogno: Should be up, maybe DNS hasn't propagated yet
18:29:58  <dbisogno>Alright, I'll keep checking back
18:30:00  <nathan7>The old API is set to maintenance mode, DNS should have propagated over the whole planet in 72h max
18:30:13  <nathan7>And I'm pretty sure our TTLs are set way lower than that
18:30:23  * joeybakerquit (Quit: Computer has gone to sleep.)
18:30:25  * c4milojoined
18:32:29  <dbisogno>Trying to create a new account it's still saying it's under maintenance, I've only been trying for the bast 2 hours or so though.
18:32:52  * indexzerojoined
18:37:30  * indexzeroquit (Ping timeout: 245 seconds)
18:41:03  * cendrizzijoined
18:41:54  <cendrizzi>Hi, I just deployed some small changes and my ops page shows that all is ok but I get a 502 when I hit my stuff
18:41:56  <cendrizzi>Any help?
18:42:18  <cendrizzi>Didn't realize you guys released the new stuff
18:42:22  <nathan7>Hey cendrizzi
18:42:24  <cendrizzi>This is my first deploy since
18:42:26  <cc123>cendrizzi: you're not alone
18:42:27  <nathan7>Username/appname?
18:42:28  <cendrizzi>Maybe something to do with that
18:42:39  <cc123>anything deployed right now seems to destroy your app
18:42:57  <cendrizzi>cendrizzi/sprinklercloud | sprinklerwebclient
18:43:05  <cendrizzi>Both
18:43:10  <cendrizzi>When did you release?
18:43:24  <cendrizzi>Major releases are so fun!
18:43:46  * stevemanueljoined
18:44:15  <cendrizzi>Bet nodejitsu is very happy that node.js is basically set in stone API wise for v1
18:44:27  <nathan7>Heh
18:44:51  <nathan7>I still have some hope for promises-in-core
18:45:07  * mokesquit (Remote host closed the connection)
18:46:24  <nathan7>cc123: Can you redeploy?
18:46:49  <cc123>ok
18:46:52  * mokesjoined
18:46:57  * joemccannquit (Quit: joemccann)
18:47:05  * tobiequit (Quit: tobie)
18:47:38  <cendrizzi>nathan7: Don't hold your breath until after v1 (which is probably a smart thing)
18:48:00  * Flyersjoined
18:48:03  <cendrizzi>I am late to the part with promises. Yeah, they look awesome.
18:48:11  <cendrizzi>*party
18:48:19  <nathan7>They're awesome for writing code in a more functional way
18:48:39  <nathan7>ForbesLindesay's latest party trick is synchronous functions with the same code as async ones
18:49:02  <cendrizzi>Isaacs, as you probably know, says they'll wait for a clear winner over callbacks.
18:49:10  <cendrizzi>nathan7: I'll take a look at that
18:49:51  <nathan7>https://github.com/ForbesLindesay/alagator pretty sweet magic
18:50:10  <cc123>@nathan7 same 502 http://prod-pushpin.jit.su/
18:50:42  * fb55quit (Remote host closed the connection)
18:50:52  * wizonesolutionsjoined
18:51:55  * fauntlejoined
18:52:17  <cendrizzi>nathan7: Too be honest for my needs I'm less concerned what they do in the core. I love how node.js is mostly user land driven for quicker innovation (so stuff like this can be incorporated easily). Seems very analogous with the dynamic nature of JS itself.
18:52:26  <nathan7>cendrizzi: Yeah
18:52:52  <cendrizzi>But I'm sure it's a big deal for you guys
18:52:54  <cendrizzi>:)
18:52:57  <nathan7>cendrizzi: but for a platform that's for building fast networked applications, having a good concurrency primitive would be awesome
18:53:06  <nathan7>cendrizzi: like, from the start
18:53:21  <cendrizzi>Yeah, good point
18:53:27  <nathan7>cendrizzi: we don't use promises at Nodejitsu btw, I just happen to be a PL nerd
18:54:12  <cendrizzi>nathan7: Yeah, will probably be easier after it's accepted as the "thing" to do more widely.
18:55:31  <jesusabdullah>what, promises?
18:55:52  <jesusabdullah>personally I'm not sure promises pay the rent
18:56:48  <cendrizzi>jesusabdullah: Having never used them I wouldn't know. Again I'm late to the party (just read them the other day following the node.js user group stuff. The syntax I saw looked really nice though.
18:57:17  <jesusabdullah>I mean
18:57:20  <jesusabdullah>I've used promises
18:57:21  <nathan7>jesusabdullah: being able to do all the usual functional things to async shit pays imho
18:57:32  <jesusabdullah>since a lot of client libraries use them
18:57:41  <cendrizzi>nathan7: Monitis just reported that my stuff recovered (at least one of them). Does that mean something was fixed?
18:57:51  <jesusabdullah>nathan7: I haven't seen a real example of this yet. Not that I deny their existence, I just haven't seen them.
18:58:17  <cendrizzi>jesusabdullah: Funny. All the client libraries I've used use callbacks.
18:58:18  * fb55joined
18:58:25  <jesusabdullah>cendrizzi: jquery?
18:58:48  <jesusabdullah>jquery's http client implements a promises api last I checked
18:58:49  <cendrizzi>jesusabdullah: Oh, I guess I just haven't used promises in them
18:59:14  <cendrizzi>jesusabdullah: Oh interesting. I need to look into it more
18:59:47  <jesusabdullah>nathan7: would love to see good examples of fp with promises
18:59:52  <cendrizzi>jesusabdullah: There is a chance I don't fully understand promises. I really just looked at one code example.
18:59:59  <nathan7>jesusabdullah: mhm
19:00:51  <nathan7>jesusabdullah: jcoglan's example is a pretty good one imho
19:01:12  <jesusabdullah>nathan7: link?
19:01:18  <nathan7>jesusabdullah: like, once I've fleshed out an idea I can convert it to callbacks and the world won't lunch me
19:01:20  <nathan7>*lynch me
19:01:23  * tylerstalderquit (Quit: Computer has gone to sleep.)
19:01:42  <nathan7>jesusabdullah: but the cognitive load involved in callbacks is far greater
19:01:58  <nathan7>jesusabdullah: because I have to explicitly sequence things as opposed to just transforming values
19:02:09  <jesusabdullah>nathan7: link?
19:02:12  <jesusabdullah>:)
19:02:14  <nathan7>yesyes
19:02:42  <nathan7>jesusabdullah: http://blog.jcoglan.com/2013/04/01/callbacks-promises-and-simplicity/
19:02:46  <cendrizzi>nathan7: What about my apps? Hehe, got a little sidetracked.
19:02:48  <nathan7>jesusabdullah: scroll down to the code
19:03:16  <nathan7>welp
19:03:19  <trygve>is there an issue with switching engine to 0.10.x?
19:03:32  * Flyersquit (Remote host closed the connection)
19:03:45  <coen-hyde>I'm not a promises fan. IMO using them internally in your lib is fine, but don't expose them. Libs exposing callbacks play nicer with each other.
19:03:45  <jesusabdullah>wth is list? He doesn't define that anywhere
19:03:58  <jesusabdullah>My talk touches on this
19:04:02  <jesusabdullah>the cascadiajs one I hope to give
19:04:15  <trygve>I'm having the Internal Server Error, npm exited with code 1 problem when changing to engine 0.10.x and deploying not
19:04:31  <cendrizzi>trygve: I think some of us are having deployment issues with the new infra so I'm not surprised you are seeing an issues with switching.
19:04:58  <nathan7>jesusabdullah: list is Promise.all
19:05:03  * tylerstalderjoined
19:05:10  <nathan7>jesusabdullah: [Promise a] -> Promise [a]
19:05:13  <trygve>I had problems earlier with 0.8.x, then it worked again so I thought I should try 0.10.x and now I got the same errors again.
19:05:41  <jesusabdullah>nathan7: yeah I mean I inferred that but it's pretty weak that he didn't do list = require('q').all or something like that
19:05:44  <nathan7>cendrizzi: Can you set your app to listen on 3000 or something?
19:05:53  <nathan7>jesusabdullah: he has his own deferred thingy and stuff
19:06:06  <nathan7>jesusabdullah: I wish he'd drop the whole monad thing, it's another war to fight
19:06:10  <jesusabdullah>yeah I just don't like incomplete code examples
19:06:19  * andreypoppjoined
19:06:19  <jesusabdullah>I see the value in this approach though
19:06:33  <jesusabdullah>Maybe I'll use promises, promises for something
19:06:45  <nathan7>you promise to use promises?
19:06:47  <nathan7>q=
19:07:01  <cendrizzi>nathan7: Yeah…. I thought it all just gets mapped to 80 anyway though
19:07:29  * tobiejoined
19:07:42  <cendrizzi>nathan7: Redeploying, port set to 3001
19:08:24  <nathan7>cendrizzi: Yeah, the port you listen on is purely internal
19:08:29  <nathan7>cendrizzi: the port-mapping code has some trouble
19:08:38  <nathan7>cc123: Can you listen on 3000 or something?
19:08:39  <nathan7>cc123: (port)
19:08:49  <nathan7>jesusabdullah: https://gist.github.com/nathan7/5279497 this kind of stuff is nice too
19:08:58  * aheckmannquit (Quit: aheckmann)
19:08:59  <nathan7>jesusabdullah: a cache for something async becomes the same as a sync one
19:09:04  <cc123>how would that work?
19:09:15  <nathan7>cc123: as in, the port your app listens on
19:09:17  <jesusabdullah>https://www.youtube.com/watch?v=vWNJlc-IylY
19:09:17  <cc123>nathan7: like my app doesn't listen on 80?
19:09:27  <nathan7>cc123: the port 80 you hit is on our load balancers
19:09:32  <cendrizzi>nathan7: and ….. done
19:09:45  <cendrizzi>Try 3001
19:09:47  <cc123>is that something i can specify in the deploy?
19:10:00  <nathan7>jesusabdullah: ohgodwhat
19:10:07  <nathan7>cc123: It's in your app code
19:10:20  <cc123>this is a meteor app
19:10:30  <nathan7>cc123: I don't know how to meteor :(
19:10:31  <cc123>is this some new change you guys have?
19:10:34  <nathan7>cc123: jitsu env set PORT 3000
19:10:39  <jesusabdullah>nathan7: the 80s motherfucker
19:10:41  <cc123>its worked fine for months
19:10:47  <nathan7>jesusabdullah: Why are you doing this to me?
19:10:52  <jesusabdullah>because
19:10:54  <jesusabdullah>promises promises
19:10:57  <nathan7>cc123: Yeah, we have some issues with the new port remapping, it's being worked on
19:11:14  * nathan7counters jesusabdullah with http://youtu.be/llDikI2hTtk
19:11:37  <cendrizzi>nathan7: So using this port is it supposed to work now?
19:11:39  * joeybakerjoined
19:11:41  <nathan7>cendrizzi: Yeah
19:11:47  <nathan7>cendrizzi: lgtm
19:12:26  <cendrizzi>Yeah, that seems to work
19:12:41  <cendrizzi>Why doesn't your status page report this problems?
19:12:45  <cendrizzi>*problem
19:12:47  <jesusabdullah>okay I desparately need to eat some fuds
19:13:04  <jesusabdullah>bbl :)
19:13:10  <nathan7>later
19:13:51  <cendrizzi>nathan7: Is there any reason to switch to port 80 when we deploy?
19:14:03  <nathan7>cendrizzi: What do you mean?
19:14:09  <cendrizzi>I do it with my stuff. Even though when run locally I use other prots
19:14:10  <cendrizzi>ports
19:14:16  * georgeredingerquit (Quit: georgeredinger)
19:14:19  <nathan7>We remap the port anyway
19:14:35  <cendrizzi>I mean for my production settings I use 80, not sure why I did that since I knew you remapped
19:14:42  <cendrizzi>Just wondering if there is any reason why
19:14:44  <nathan7>But the stuff for remapping ports under 1024 has issues currently
19:14:59  <nathan7>Basically, when you do .listen(), we have a hook to know the port
19:15:26  <cendrizzi>nathan7: So I might as well just keep the same port as local development (all over 3000 BTW)
19:15:29  <nathan7>cendrizzi: Yep
19:15:45  * coen-hydequit (Quit: coen-hyde)
19:15:53  <nathan7>I don't even put a port in for things that only go onto Nodejitsu
19:16:08  <nathan7>But.. that's port 0, which the OS remaps, which also isn't handled right atm
19:16:19  <nathan7>Rest assured, jcrugzz will return in a bit and work some magic on the code
19:18:46  <cendrizzi>nathan7: Ok, that works
19:20:03  <nathan7>cendrizzi: [=
19:23:18  * parallelquit (Remote host closed the connection)
19:24:03  <cc123>nathan7: i had to switch hosts to avoid downtime, but the url redirects to the other host so I'm thinking it might be working
19:24:20  <cc123>thanks for your help
19:24:33  <cc123>i really wish you guys would email us about these things...
19:24:43  <cc123>so i could make time to stand by
19:27:09  <nathan7>cc123: Yeah, we're looking into a better mechanism for informing people of upgrades and such
19:27:38  <nathan7>Upgrades like this are unlikely to ever happen again though
19:27:58  <nathan7>We've rebuilt everything to be much more robust than it ever was
19:30:44  * dfmcpheejoined
19:31:24  * dfmcpheepart
19:34:04  * coen-hydejoined
19:34:43  * coen-hydequit (Client Quit)
19:35:50  * dfmcpheejoined
19:36:22  * dfmcpheepart
19:40:10  * coen-hydejoined
19:40:42  * tylerstalderquit (Ping timeout: 264 seconds)
19:41:41  * sol_invictusquit (Remote host closed the connection)
19:44:46  <stevemanuel>are logs still under maintenance? cant get anything besides 'Streaming logging information' out of webops or a Sokcet hang up from ` $ jitsu logs`
19:47:39  <nathan7>stevemanuel: Can you try updating your jitsu?
19:48:05  <stevemanuel>@nathan7, it seems to only have happened after I updated just about 30 min ago
19:48:15  * frenchtoastjoined
19:48:24  <stevemanuel>jitsu -v gives me 0.13.0
19:49:21  <Sly>stevemanuel: can you check `jitsu config list` and make sure it has something like
19:49:24  <Sly>data: logs: {
19:49:24  <Sly>data: host: 'logs.nodejitsu.com',
19:49:24  <Sly>data: port: 443,
19:49:25  <Sly>data: protocol: 'https'
19:49:27  <Sly>data: },
19:49:34  <Sly>If not, that needs to be added into ~/.jitsuconf
19:50:36  * nukeninsystemsjoined
19:50:56  <stevemanuel>Ok. it didn't have that. Is it supposed to go within the exsiting object or outside of it
19:53:03  <Sly>In that object. :)
19:53:31  <stevemanuel>ok, now I'm getting: warn: No logs for reachsocket-snipdo in specified timespan
19:54:18  <nathan7>Can you jitsu start your app?
19:54:24  <nathan7>It's probably still on the old cloud
19:54:41  * MrDHatchanged nick to MrDHat|offline
19:58:37  * paralleljoined
20:01:06  * frenchtoastquit (Ping timeout: 264 seconds)
20:04:39  * kevino80joined
20:05:38  * kevino80quit (Remote host closed the connection)
20:07:52  * brandonrvaughanjoined
20:12:10  * japandroidjoined
20:13:18  <brandonrvaughan>just saw the tweet about the 0.10.16 upgrade how/where do I see when and if u are planning on upgrading?
20:16:24  * aheckmannjoined
20:16:33  <mmalecki>brandonrvaughan: I'm upgrading all servers now
20:17:00  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:17:21  <mmalecki>this CVE is kind of bullshit tho, issue hasn't been publicized yet
20:22:17  <brandonrvaughan>cool so where do i find which versions are being used?
20:22:51  <mmalecki>we still have to implement that in jitsu, actually
20:22:54  <mmalecki>there's an issue
20:23:25  <nathan7>it's apparently a mere local DoS for node
20:25:27  <mmalecki>nathan7: oh? the CVE description makes it sound serious
20:25:58  <nathan7>mmalecki: for Chromium it's remote
20:26:03  <nathan7>mmalecki: because browserness
20:26:16  <nathan7>as long as your node app has no remote code execution, it's a local DoS
20:26:21  <nathan7>https://github.com/joyent/node/issues/5973
20:26:31  * parallelquit (Remote host closed the connection)
20:27:05  <mmalecki>ohlolright
20:29:33  * indexzerojoined
20:32:13  <`3rdEden>nathan7: Yeah I was just wondering the same thing
20:32:26  <`3rdEden>I don't even understand why it was release as "security" patch
20:32:44  <`3rdEden>It's not like an attacker can use it to fuck up your server..
20:34:48  <mmalecki>yeah, it's not even harmful to our infrastructure. it'd be with haibu-carapace, but not with forza, etc.
20:35:01  <nathan7>I can imagine cases where it
20:35:05  <nathan7>'d affect security
20:35:08  <mmalecki>but you gotta do what you gotta do
20:35:12  <nathan7>but they're rare
20:35:29  * standoojoined
20:35:30  * standooquit (Remote host closed the connection)
20:35:47  * brandonrvaughanquit (Quit: brandonrvaughan)
20:35:51  * paralleljoined
20:37:06  * standoojoined
20:37:11  * cronopiojoined
20:37:26  * arnaldocapoquit (Quit: arnaldocapo)
20:39:24  * aheckmannquit (Quit: aheckmann)
20:40:05  * cc123quit (Quit: cc123)
20:44:58  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
20:45:08  * fb55quit (Remote host closed the connection)
20:53:01  * jgablejoined
20:58:39  * towskijoined
20:58:58  * steidajoined
20:59:47  <steida>maintenance should be done ideally at 2:00 a.m., not p.m.
20:59:51  * dbisognoquit (Ping timeout: 250 seconds)
21:00:46  * Hebojoined
21:01:56  <jcrugzz>steida: what are you seeing?
21:02:28  <steida>I can not login: "We're currently undergoing maintenance. Please check #nodejitsu on irc.freenode.net for updates."
21:02:38  <jcrugzz>steida: is this from home or webops?
21:02:49  * bzooquit (Remote host closed the connection)
21:02:53  <steida>https://www.nodejitsu.com
21:03:05  <jcrugzz>steida: can you try from webops.nodejitsu.com?
21:03:25  * bzoojoined
21:03:43  * bzooquit (Read error: Connection reset by peer)
21:04:10  * bzoojoined
21:05:52  * coen-hydequit (Quit: coen-hyde)
21:07:42  <steida>webops works
21:07:46  <steida>fa
21:07:49  * steidaquit (Quit: Page closed)
21:08:47  * bzooquit (Remote host closed the connection)
21:09:09  * Samuel_Roldanquit (Ping timeout: 264 seconds)
21:09:13  * bzoojoined
21:09:41  <daviddia_>Strang, I can sign in through webops.nodejitsu.com but not in nodejitsu.com
21:10:41  * Nevtepquit (Ping timeout: 250 seconds)
21:11:15  * japandroidquit (Ping timeout: 245 seconds)
21:12:18  <mmalecki>daviddia_: yeah, `3rdEden is on it :)
21:12:36  * daviddia_changed nick to daviddias
21:12:44  <daviddias>@mmalecki great! Thanks :)
21:12:58  <`3rdEden>daviddias: should be fixed in 10 - 20 min
21:13:26  * bzooquit (Ping timeout: 240 seconds)
21:15:06  * mokesquit (Remote host closed the connection)
21:15:41  * mokesjoined
21:16:36  * japandroidjoined
21:16:36  * mokesquit (Read error: Connection reset by peer)
21:17:01  * kscully27quit (Read error: Connection reset by peer)
21:17:29  * kscully27joined
21:18:33  * mokesjoined
21:18:35  * andreypoppquit (Quit: andreypopp)
21:18:46  * mokesquit (Read error: Connection reset by peer)
21:20:54  * mokesjoined
21:22:53  * `3rdEdendaviddias: mmalecki: Works again!
21:23:35  <daviddias>Awesome! Thanks @`3rdEden
21:30:36  * ionellaquit (Remote host closed the connection)
21:32:31  * jgablequit (Quit: Computer has gone to sleep.)
21:33:38  * japandroidquit (Quit: Lost terminal)
21:33:44  * jgablejoined
21:34:23  <nukeninsystems>im getting a 502 Reached max retries limit
21:34:33  <nukeninsystems>http://partyradar.jit.su/api/v1/photo/list
21:34:35  <nukeninsystems>any ideas?
21:34:53  <jcrugzz>nukeninsystems: username/appname?
21:35:06  <nukeninsystems>username: nukeninsystems
21:35:10  <nukeninsystems>appname: partyradar
21:37:03  <nukeninsystems>actually ... might be my fault .. i forgot to add underscore to the packages.json i just realized
21:37:29  <jcrugzz>nukeninsystems: that will do it ;)
21:37:34  * cendrizziquit (Remote host closed the connection)
21:46:38  * coen-hydejoined
21:48:51  * c4miloquit (Remote host closed the connection)
21:49:30  * redirquit (Quit: . … _ … . …._)
21:51:22  * andreypoppjoined
21:51:27  * redirjoined
21:52:01  * tobiequit (Quit: tobie)
21:55:19  * bobbybuilderquit (Ping timeout: 250 seconds)
21:57:42  * alxjoined
21:58:29  * redirquit (Ping timeout: 248 seconds)
22:08:19  * redirjoined
22:08:55  * towskiquit (Remote host closed the connection)
22:10:51  * indexzeroquit (Quit: indexzero)
22:11:03  * parallelquit (Remote host closed the connection)
22:15:27  * redirquit (Quit: . … _ … . …._)
22:16:23  * alxquit (Remote host closed the connection)
22:17:55  * c4milojoined
22:18:52  * andreypoppquit (Quit: andreypopp)
22:21:18  * kscully27quit (Remote host closed the connection)
22:21:31  * jgablequit (Read error: Connection reset by peer)
22:24:29  * andreypoppjoined
22:29:15  * mokesquit (Remote host closed the connection)
22:30:06  * itzmjauzquit (Ping timeout: 264 seconds)
22:30:28  * nathan7quit (Ping timeout: 264 seconds)
22:31:04  * julianduquejoined
22:32:01  * mokesjoined
22:34:19  * bzoojoined
22:35:04  * cendrizzijoined
22:35:49  * Slaytorsonquit (Ping timeout: 246 seconds)
22:36:28  * paralleljoined
22:36:54  * parallelquit (Remote host closed the connection)
22:38:32  * nukeninsystemsquit (Quit: Page closed)
22:41:02  * standooquit (Ping timeout: 240 seconds)
22:42:27  * andreypoppquit (Quit: andreypopp)
22:43:22  * redirjoined
22:47:46  * `3rdEdenchanged nick to `3E|Zzz
22:54:01  * alxjoined
22:54:31  * coen-hyde_joined
22:55:00  * coen-hydequit (Ping timeout: 260 seconds)
22:55:01  * coen-hyde_changed nick to coen-hyde
22:57:11  * standoojoined
22:57:12  * standooquit (Remote host closed the connection)
22:57:23  * standoojoined
22:59:15  * fb55joined
23:03:36  * fb55quit (Ping timeout: 256 seconds)
23:04:55  * Samuel_Roldanjoined
23:07:35  * redirquit (Quit: . … _ … . …._)
23:09:12  * bzooquit (Remote host closed the connection)
23:09:48  * bzoojoined
23:10:03  * papachanjoined
23:13:50  * bzooquit (Ping timeout: 240 seconds)
23:14:58  * tobiejoined
23:16:19  * wizonesolutionsquit (Ping timeout: 240 seconds)
23:20:56  * mokesquit (Remote host closed the connection)
23:21:49  * vlad_joined
23:23:04  * spopequit (Ping timeout: 268 seconds)
23:24:11  * wizonesolutionsjoined
23:24:15  <vlad_>Hi
23:24:17  * Heboquit
23:25:16  <vlad_>I'm deploying an app that has a node_env of 'development' but for some reason the app is using node_env 'production'. Have you seen this?
23:25:35  <julianduque>vlad_: yes, we always deploy to production
23:25:50  <julianduque>vlad_: we are working on support multi env
23:26:07  * Seba_joined
23:26:15  <julianduque>Seba_: saludos
23:26:26  <Seba_>Hola Julian
23:26:44  <julianduque>Seba_: ya estoy mirando, viste la nota del directorio public en wagaduu-cdn?
23:26:51  <Seba_>wagaservices que es una aplicacion API REST tambien tiene el mismo problema
23:27:05  <Seba_>no, qué nota?
23:28:10  <julianduque>Seba_: te envie un correo con el error que me retorna wagaduu-cdn
23:28:27  <vlad_>but it was always working before with NODE_ENV= 'development'
23:28:31  * InconceivableBquit (Quit: Computer has gone to sleep.)
23:28:36  <vlad_>Its just an environment variable
23:29:37  * jgablejoined
23:30:12  <julianduque>Seba_: como puedo probar wagaservices?
23:30:16  <Seba_>Pero los 3 servers dan el mismo error
23:30:58  <Seba_>esta caído
23:31:09  <Seba_>andaba hasta hace unos minutos
23:31:11  <Seba_>se prueba por rest
23:31:21  * Samuel_Roldanquit (Ping timeout: 264 seconds)
23:31:29  <julianduque>Ayudame probando static y services, ya estoy mirando que pasa con cdn
23:31:47  <Seba_>http://{{server}}:{{port}}/api/public/login/facebook
23:32:08  <Seba_>http://wagaservices.jit.su/api/public/login/facebook
23:32:38  * kscully27joined
23:33:01  * Hebojoined
23:35:52  * diogogmtquit (Quit: diogogmt)
23:36:02  <Seba_>claro, decime lo que necesites
23:37:57  * kscully27quit (Ping timeout: 264 seconds)
23:38:56  <Seba_>julian, me desconecto unos minutos, y vuelvo, pls, necesito ayuda, no andan ninguno de los 3 servers
23:39:03  <Seba_>y no cambiamos nada de enviroments
23:39:15  <julianduque>Seba_: listo ya me encargo, te dejo saber por correo
23:42:45  * cronopioquit (Ping timeout: 264 seconds)
23:43:39  * Seba_quit (Ping timeout: 250 seconds)
23:44:31  * katowulfquit (Ping timeout: 250 seconds)
23:44:31  * dfmcphee_joined
23:44:51  * Heboquit
23:48:21  * caseywebdevjoined
23:49:05  * dfmcphee_changed nick to dfmcphee
23:49:51  <caseywebdev>I seem to be getting logs from someone else's app instead of my own
23:49:51  <daviddias>Not sure if I did something wrong, after updating jitsu-cli and deploying, the old app {appDomain}.jit.su stop responding and in the end of the deploy it's referenced a {appDomain}.nodejitsu.com that doesn't reply either
23:51:02  <daviddias>@mmalecki @julianduque any ideas? :)
23:51:06  <julianduque>daviddias: what is the sudbomain?
23:51:24  <daviddias>thenodefirm-dev
23:52:32  * dfmcpheepart
23:52:34  * stevemanueljoined
23:54:07  <stevemanuel>`jitsu start` pillaged my apps.. 502 Reached max retries limit cant do anything now. although my webops says its running
23:55:56  * mokesjoined