00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:02:54  * anoemijoined
00:09:19  * admcquit (Quit: Leaving.)
00:14:03  * bzooquit (Remote host closed the connection)
00:14:39  * bzoojoined
00:19:22  * bzooquit (Ping timeout: 268 seconds)
00:20:43  * RORgasmjoined
00:23:42  * evangeni_quit (Read error: Connection reset by peer)
00:25:07  * jcrugzzquit (Ping timeout: 264 seconds)
00:25:08  * RORgasmquit (Ping timeout: 255 seconds)
00:32:23  * defunctzombiechanged nick to defunctzombie_zz
00:33:20  * bzoojoined
00:34:13  * bzooquit (Remote host closed the connection)
00:34:40  * bzoojoined
00:36:41  * erichoceanjoined
00:38:31  * bzooquit (Read error: Connection reset by peer)
00:38:46  * bzoojoined
00:55:23  * jcrugzzjoined
01:05:16  * evangeni_joined
01:06:00  * defunctzombie_zzchanged nick to defunctzombie
01:15:16  * anoemiquit (Quit: anoemi)
01:18:24  * jgablejoined
01:20:34  * zkirillquit (Quit: zkirill)
01:26:52  * anoemijoined
01:35:37  * evangeni_quit (Remote host closed the connection)
01:41:39  * c4milojoined
02:06:35  * ipalreadytakenjoined
02:08:19  * silv3rwindquit (Quit: Leaving)
02:14:50  * TooTallNatejoined
02:20:57  * jgablequit (Quit: Computer has gone to sleep.)
02:22:15  * defunctzombiechanged nick to defunctzombie_zz
02:24:30  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
02:59:10  * cendrizzijoined
03:00:06  <cendrizzi>The redis stuff down?
03:00:19  <cendrizzi>My stuff keeps failing because of the redis stuff
03:00:25  <cendrizzi>Haven't changed my code in a bit
03:01:33  * frenchtoastquit (Ping timeout: 268 seconds)
03:16:02  * bzooquit (Remote host closed the connection)
03:16:30  * bzoojoined
03:21:28  * bzooquit (Ping timeout: 276 seconds)
03:23:24  * GoddeRjoined
03:33:11  * InconceivableBjoined
04:02:34  * defunctzombie_zzchanged nick to defunctzombie
04:02:55  * GoddeRquit
04:17:04  * anoemi_joined
04:17:09  * i_m_cajoined
04:18:31  * anoemiquit (Ping timeout: 264 seconds)
04:18:31  * anoemi_changed nick to anoemi
04:21:27  * RORgasmjoined
04:21:38  * Heboquit
04:23:15  * anoemiquit (Quit: anoemi)
04:24:11  * zkirilljoined
04:25:53  * RORgasmquit (Ping timeout: 255 seconds)
04:29:16  * defunctzombiechanged nick to defunctzombie_zz
04:33:09  * poormanquit (Quit: Closed my MacBook Air lid. ZZZzzz…)
04:36:55  * c4miloquit (Remote host closed the connection)
04:39:11  * zkirillquit (Quit: zkirill)
04:53:15  * bzoojoined
04:54:01  * ipalreadytakenquit (Remote host closed the connection)
04:57:57  * fomatinquit (Quit: Computer has gone to sleep.)
05:16:16  * InconceivableBquit (Quit: Computer has gone to sleep.)
05:20:58  * generalissimoquit (Remote host closed the connection)
05:33:00  * Nodejitsu-Githubjoined
05:33:00  <Nodejitsu-Github>[godot] jcrugzz pushed 1 new commit to moar-docs: http://git.io/x8wXsg
05:33:00  <Nodejitsu-Github>godot/moar-docs 3046f33 Jarrett Cruger: [docs api] update for the new movingAverage api
05:33:00  * Nodejitsu-Githubpart
05:51:20  * bzooquit (Remote host closed the connection)
05:51:53  * bzoojoined
05:54:03  * erichoceanquit (Quit: erichocean)
05:56:41  * bzooquit (Ping timeout: 268 seconds)
06:04:25  * tobiejoined
06:18:08  * leichtgewichtjoined
06:21:08  * Samuel_Roldanjoined
06:21:51  * RORgasmjoined
06:26:29  * RORgasmquit (Ping timeout: 255 seconds)
06:38:57  * mdedetrichquit (Quit: Computer has gone to sleep.)
07:06:12  * atomlessjoined
07:09:35  * erichoceanjoined
07:25:15  * `3Echanged nick to `3rdEden
07:30:13  * admcjoined
07:30:46  * Samuel_Roldanquit (Quit: Samuel_Roldan)
07:38:16  * zkirilljoined
07:45:55  * sreeixjoined
07:48:19  * Samuel_Roldanjoined
07:52:05  * vector_tquit (Ping timeout: 246 seconds)
08:14:49  * chrisdotcodequit (Ping timeout: 268 seconds)
08:15:21  * atomlessquit (Quit: My iMac has gone to sleep. ZZZzzz…)
08:22:16  * RORgasmjoined
08:26:41  * RORgasmquit (Ping timeout: 248 seconds)
08:32:11  * Siyfionjoined
08:33:42  <Siyfion>Interestingly, on Friday my application crashed due to being out of memory; however I've since installed memwatch and profiled it fairly extensively, and there isn't a memory leak as far as I can tell...
08:33:58  <Siyfion>is it possible that the drone got a bit messed up somehow?
08:41:41  * jetiennejoined
08:48:19  * Samuel_Roldanquit (Quit: Samuel_Roldan)
08:48:45  * benjaminbenbenjoined
08:56:06  * ChrisMathesonjoined
09:01:56  * admcquit (Quit: Leaving.)
09:11:08  <tobie>`3rdEden: hey, still bumping into auto deploy issues with travis/github setup. Any updates?
09:11:20  <`3rdEden>swaagie: ^ ?
09:13:47  <`3rdEden>tobie: I honestly have no idea, what the progress is on it or why it's still failing but swaagie might know as he had contact with GH about it
09:14:33  <tobie>`3rdEden: ok, cool.
09:14:41  <swaagie>tobie: what kind of issues exactly?
09:15:01  <swaagie>do you have username for me please, so I can look at the logs?
09:15:09  <tobie>not-deploying despite successful travis output
09:15:13  <tobie>swaagie: yup
09:15:21  <tobie>username: tobie
09:15:32  <swaagie>:)
09:15:44  <tobie>app: specref.jit.su/
09:16:07  <tobie>src code: https://github.com/tobie/specref
09:16:39  <tobie>travis yml: https://github.com/tobie/specref/blob/master/.travis.yml
09:16:50  * Nodejitsu-Githubjoined
09:16:50  <Nodejitsu-Github>[node-http-proxy] yawnt created 0.10.x (+1 new commit): http://git.io/-9gpXg
09:16:50  <Nodejitsu-Github>node-http-proxy/0.10.x d561e27 yawnt: [fix] refactor
09:16:50  * Nodejitsu-Githubpart
09:22:52  <swaagie>tobie: btw judging from your initial request to `3rdEden have you asked for support before? just wondering if someone of us perhaps found any problems already ;)
09:23:29  <tobie>swaagie: only through irc. A while back.
09:23:42  <tobie>Think `3rdEden mentioned it was a known issue at the time.
09:24:09  <tobie>Something about GitHub having an incorrect content length header for their tarballs.
09:24:10  <swaagie>yeah but that has long been resolved
09:24:16  <tobie>oh.
09:24:20  <swaagie>or rather we found a way around it
09:24:46  <tobie>so auto-deploy hasn't worked properly since for me.
09:24:47  <swaagie>tobie: the last deploy failed due to bad credentials
09:25:15  <tobie>bad credentials where?
09:25:37  <tobie>or rather: how do I fix that.
09:25:45  <tobie>s/./?/
09:26:56  <swaagie>tobie: sec checking which ones exactly :)
09:27:02  <tobie>swaagie: ty
09:29:15  <swaagie>it seems the deploy failed, so that would be the token created in step 3 of https://www.nodejitsu.com/getting-started-with-github/ and added to github in step 6, could you try to regenerate it and try agian please?
09:31:01  <tobie>yup
09:36:00  * Hounddogjoined
09:42:01  * sreeixquit (Ping timeout: 246 seconds)
09:42:34  * sreeixjoined
09:45:03  * zkirillquit (Quit: zkirill)
09:50:23  <tobie>swaagie: now it's travis which isn't running my PR CI test. :(
09:50:40  <swaagie>might take a while
09:50:47  <swaagie>travis is sometimes busy ;)
09:51:22  <tobie>Weird though, how GH doesn't show Travis is busy running the tests
09:51:54  <tobie>swaagie: https://github.com/tobie/specref/pull/15
09:52:43  <swaagie>not sure if the travis api allows it
09:52:54  <swaagie>should be findable in the que though
09:53:40  <tobie>used to work too.
09:54:37  <tobie>swaagie: https://travis-ci.org/tobie/specref/builds/8381668
09:55:03  <swaagie>ah :)
09:55:47  <swaagie>travis seems slow today
10:01:55  * Nodejitsu-Githubjoined
10:01:55  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/ePGf0g
10:01:55  <Nodejitsu-Github>node-http-proxy/0.10.x ac92c65 yawnt: [refactor] start working on forwardStream
10:01:55  * Nodejitsu-Githubpart
10:10:23  * Nodejitsu-Githubjoined
10:10:23  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/jPFY4w
10:10:23  <Nodejitsu-Github>node-http-proxy/0.10.x c278fb8 yawnt: [fix] now you can pipe()
10:10:23  * Nodejitsu-Githubpart
10:13:05  * Hounddogquit (Read error: Connection reset by peer)
10:15:32  * Jester831quit (Quit: Leaving...)
10:18:20  * Nodejitsu-Githubjoined
10:18:20  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/cBaKHw
10:18:20  <Nodejitsu-Github>node-http-proxy/0.10.x 4a97e8c yawnt: [fix] typo
10:18:20  * Nodejitsu-Githubpart
10:22:37  * RORgasmjoined
10:26:54  * RORgasmquit (Ping timeout: 240 seconds)
10:28:40  * sreeixquit (Quit: sreeix)
10:29:52  * travis-cijoined
10:29:52  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#182 (0.10.x - d561e27 : yawnt): The build passed.
10:29:52  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/commit/d561e271cf78
10:29:52  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8381153
10:29:52  * travis-cipart
10:40:17  <mmalecki>yawnt: PING
10:40:21  <mmalecki>yawnt: PING PING PING
10:40:24  <mmalecki>yawnt: I NEED YOU
10:49:51  * julianduquejoined
10:50:32  * sreeixjoined
10:55:59  * ChrisMathesonquit (Quit: ChrisMatheson)
10:56:39  <swaagie>tobie it seems travis was finally done, no success though, inspecting what the errors are atm
10:59:51  * atomlessjoined
11:00:58  * frenchtoastjoined
11:01:17  <swaagie>tobie: ow I see you didnt merge the PR yet, that explains it :)
11:01:34  <swaagie>give me a ping when your going to merge it
11:01:41  <swaagie>please :)
11:06:25  * swaagiechanged nick to swaagie[food]
11:06:46  * st_lukejoined
11:07:00  <mmalecki>st_luke: http://vimeo.com/62906245
11:11:34  * Nodejitsu-Githubjoined
11:11:34  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/4cgDwA
11:11:34  <Nodejitsu-Github>node-http-proxy/0.10.x 44097a8 yawnt: [api] first draft of ProxyStream
11:11:34  * Nodejitsu-Githubpart
11:11:57  * travis-cijoined
11:11:58  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#183 (0.10.x - ac92c65 : yawnt): The build passed.
11:11:58  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/d561e271cf78...ac92c65ca500
11:11:58  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8382063
11:11:58  * travis-cipart
11:15:15  * st_lukequit (Remote host closed the connection)
11:17:14  * julianduquequit (Quit: Bye)
11:32:24  * travis-cijoined
11:32:24  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#184 (0.10.x - c278fb8 : yawnt): The build passed.
11:32:24  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/ac92c65ca500...c278fb8a0aa6
11:32:24  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8382265
11:32:24  * travis-cipart
11:37:19  * jetiennequit (Quit: jetienne)
11:38:29  * miklquit (Quit: Connection reset by Peer Gynt)
11:48:28  * wdzydzejoined
11:51:32  * ChrisMathesonjoined
11:52:54  * frenchtoastquit (Ping timeout: 240 seconds)
12:05:24  * swaagie[food]changed nick to swaagie
12:08:39  * thealanwattsriotjoined
12:09:27  * mdedetrichjoined
12:21:32  * jcrugzzquit (Ping timeout: 256 seconds)
12:23:00  * RORgasmjoined
12:27:23  * RORgasmquit (Ping timeout: 255 seconds)
12:35:43  * sirkitreejoined
12:36:20  <swaagie>tobie: \o/ success
12:36:22  <swaagie>:)
12:36:41  <tobie>ok, cool. well, thanks a bunch.
12:37:12  <swaagie>tobie: if you run into any problems while using CI/webhooks just ping us again as we are still opting for a complete rewrite of that piece of architecture :)
12:37:31  <tobie>Well, https://webops.nodejitsu.com/apps/specref is till running the old version of the app.
12:38:12  <tobie>swaagie: ^
12:39:49  <tobie>swaagie: merge is still in the queue: https://travis-ci.org/tobie/specref/builds/8385819
12:40:23  <tobie>swaagie: now curious as to how you define success. :D
12:40:47  <swaagie>tobie: hmm I just judged it from the state of couch
12:41:07  * travis-cijoined
12:41:07  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#185 (0.10.x - 4a97e8c : yawnt): The build failed.
12:41:07  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/c278fb8a0aa6...4a97e8c02ea7
12:41:07  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8382434
12:41:07  * travis-cipart
12:42:21  <swaagie>tobie: e.g. the button https://webhooks.nodejitsu.com/tobie/specref.png
12:42:44  <swaagie>and from travis#82
12:43:15  <tobie>swaagie: button is missing an active snapshot number.
12:43:23  <swaagie>I'm not sure about the webops versioning
12:43:26  <swaagie>tobie: good point
12:43:31  <swaagie>that would be an improvement
12:43:37  <swaagie>adding to the list
12:43:48  <tobie>swaagie: pushed 0.0.7
12:43:57  <tobie>Still running 0.0.6-6 afaik
12:44:45  <swaagie>tobie: I can confirm that
12:44:48  <tobie>swaagie: but that's due to the travis backlog
12:45:23  <tobie>which it tied to: http://status.travis-ci.com/incidents/hdkykzsk954k
12:46:13  <swaagie>hmm
12:47:06  <swaagie>I'll keep an eye out until the backlog is clean
12:47:15  * travis-cijoined
12:47:15  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#186 (0.10.x - 44097a8 : yawnt): The build was broken.
12:47:15  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/4a97e8c02ea7...44097a85a744
12:47:15  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8383767
12:47:15  * travis-cipart
12:55:15  * ChrisMathesonquit (Quit: ChrisMatheson)
12:55:41  * frenchtoastjoined
12:57:04  * anoemijoined
13:08:51  * kenperkinsquit (Quit: Textual IRC Client: http://www.textualapp.com/)
13:09:25  * sreeixquit (Ping timeout: 256 seconds)
13:09:27  * sreeix_joined
13:10:44  * devdazedjoined
13:11:05  * Nodejitsu-Githubjoined
13:11:05  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/7peXsw
13:11:05  <Nodejitsu-Github>node-http-proxy/0.10.x 09fb14e yawnt: [api] proxystream
13:11:05  * Nodejitsu-Githubpart
13:11:49  * kenperkinsjoined
13:12:26  * jcrugzzjoined
13:14:04  * mdedetrichquit (Quit: Computer has gone to sleep.)
13:18:39  * johnmartyjoined
13:21:38  * brianloveswordsquit (Ping timeout: 248 seconds)
13:23:31  * anoemiquit (Quit: anoemi)
13:24:40  * thealanwattsriotquit (Ping timeout: 276 seconds)
13:24:54  * c4milojoined
13:25:10  * brianloveswordsjoined
13:27:11  * thealanwattsriotjoined
13:33:26  * atomlessquit (Quit: My iMac has gone to sleep. ZZZzzz…)
13:33:38  * erichoceanquit (Quit: erichocean)
13:35:59  * jetiennejoined
13:35:59  * generalissimojoined
13:37:51  * InconceivableBjoined
13:38:36  * erichoceanjoined
13:42:01  * c4miloquit (Remote host closed the connection)
13:43:11  * fomatinjoined
13:48:11  * anoemijoined
13:48:43  * thealanwattsriotquit (Ping timeout: 276 seconds)
13:48:55  * jgablejoined
13:50:40  * thealanwattsriotjoined
13:52:15  * jetiennequit (Quit: jetienne)
13:54:46  * Remijoined
13:55:05  * Remichanged nick to Guest31345
13:57:07  * fomatinquit (Quit: Computer has gone to sleep.)
14:04:28  * klaemojoined
14:13:53  * bahaaldi_joined
14:14:19  * bahaaldi_quit (Remote host closed the connection)
14:16:06  * Samuel_Roldanjoined
14:18:28  * brianloveswordsquit (Excess Flood)
14:20:01  * RORgasmjoined
14:20:40  * brianloveswordsjoined
14:20:41  * jetiennejoined
14:22:29  * generalissimoquit (Remote host closed the connection)
14:27:00  * erichoceanquit (Quit: erichocean)
14:27:36  * c4milojoined
14:28:05  * bzoojoined
14:28:29  * fomatinjoined
14:29:01  * defunctzombie_zzchanged nick to defunctzombie
14:32:48  * travis-cijoined
14:32:48  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#187 (0.10.x - 09fb14e : yawnt): The build is still failing.
14:32:48  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/44097a85a744...09fb14e3f023
14:32:48  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/8386759
14:32:48  * travis-cipart
14:32:50  * jcrugzzquit (Ping timeout: 268 seconds)
14:41:19  * thealanwattsriotquit (Ping timeout: 264 seconds)
14:43:29  * anoemiquit (Quit: anoemi)
14:44:09  * thealanwattsriotjoined
14:47:55  * Nodejitsu-Githubjoined
14:47:55  <Nodejitsu-Github>[http-server] indexzero pushed 7 new commits to master: http://git.io/9ar6-g
14:47:55  <Nodejitsu-Github>http-server/master c2f1786 Michael Bradley, Jr: bump all deps
14:47:55  <Nodejitsu-Github>http-server/master 20f39d6 Michael Bradley, Jr: bump all dev deps
14:47:55  <Nodejitsu-Github>http-server/master de54a27 Michael Bradley, Jr: directory listings option, per node-ecstatic
14:47:55  * Nodejitsu-Githubpart
14:48:51  * Nodejitsu-Githubjoined
14:48:51  <Nodejitsu-Github>[http-server] indexzero pushed 1 new commit to master: http://git.io/CsEIyw
14:48:51  <Nodejitsu-Github>http-server/master 3ce7ece indexzero: [dist] Version bump. 0.5.5
14:48:51  * Nodejitsu-Githubpart
14:53:07  * thealanwattsriotquit (Ping timeout: 256 seconds)
14:55:46  * thealanwattsriotjoined
14:56:37  <tobie>swaagie: no dice.
14:56:45  * wdzydzequit (Ping timeout: 250 seconds)
14:56:59  <tobie>swaagie: travis build successfully completed: https://travis-ci.org/tobie/specref/builds/8385819
14:57:31  <tobie>swaagie: yet nodejitsu still running previous snapshot.
14:58:05  <tobie>swaagie: https://webops.nodejitsu.com/apps/specref
14:59:30  <kenperkins>mmalecki: what's with all the streams2 hate
15:01:19  <swaagie>tobie: it seems it failed due to bad credentials again, but I you refreshed them right?
15:01:27  <tobie>I did.
15:01:43  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
15:01:45  <swaagie>tobie then I'll have to investigate if something is going haywire
15:01:52  <swaagie>other then issues we already encountered
15:01:55  <tobie>I regenerated creds using the node API
15:02:10  <tobie>s/node/nodejitsu/
15:02:43  <tobie>And added them to github
15:02:54  <tobie>swaagie: is there a way for me to check those creds are OK?
15:03:48  <swaagie>well it should just be the token, sec let me check
15:06:51  * chrisdotcodejoined
15:13:20  * generalissimojoined
15:13:22  <swaagie>tobie see pm in a sec
15:19:47  * thealanwattsriotjoined
15:22:34  <mmalecki>someone pinged me?
15:23:07  <mmalecki>kenperkins: it's just a terrible API
15:25:14  * defunctzombiechanged nick to defunctzombie_zz
15:27:01  * sreeix_quit (Quit: sreeix_)
15:28:43  * cendrizziquit (Ping timeout: 264 seconds)
15:31:45  * jetiennequit (Quit: jetienne)
15:34:45  * cendrizzijoined
15:34:49  <cendrizzi>Can someone confirm if there was a redis problem last night?
15:50:36  * bzooquit (Remote host closed the connection)
15:51:09  * bzoojoined
15:56:05  * bzooquit (Ping timeout: 268 seconds)
16:00:14  * Jester831joined
16:02:13  * jcrugzzjoined
16:10:38  * Guest31345quit (Quit: Guest31345)
16:19:16  * chrisdotcodequit (Ping timeout: 246 seconds)
16:21:40  * anoemijoined
16:31:31  * stevemanueljoined
16:31:56  * bzoojoined
16:32:53  * ChrisMathesonjoined
16:34:07  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
16:38:04  * swaagiechanged nick to swaagie[bbl]
16:38:44  * lwicksjoined
16:43:49  * Remijoined
16:44:12  * Remichanged nick to Guest40945
16:44:18  * Guest40945quit (Client Quit)
16:45:03  * defunctzombie_zzchanged nick to defunctzombie
16:46:06  * atomlessjoined
16:55:23  * c4miloquit (Remote host closed the connection)
16:57:43  * Samuel_Roldanquit (Quit: Samuel_Roldan)
17:04:16  * thealanwattsriotjoined
17:09:13  * Samuel_Roldanjoined
17:09:45  * zkirilljoined
17:13:41  * rosskjoined
17:15:38  * lwicksquit (Ping timeout: 268 seconds)
17:26:26  * Siyfionquit (Quit: Leaving)
17:30:39  * admcjoined
17:30:49  * upshootjoined
17:32:24  * benjaminbenbenquit (Quit: benjaminbenben)
17:32:26  * ChrisMathesonquit (Quit: ChrisMatheson)
17:34:51  * ChrisMathesonjoined
17:35:02  * benjaminbenbenjoined
17:37:44  * sreeixjoined
17:38:29  <upshoot>I'm looking at an example express app, and see the configuration data is all in a config.js, including the API keys for Amazon, Facebook, etc. I see that I can set those as ENV values in nodejitsu and heroku. What is the best practice and why? I don't like putting my api keys into version control.
17:39:09  <upshoot>But it seems like it's likely to be easy for a hacker to access the ENV values -- but I'm not sure if that's true or not.
17:41:26  <upshoot>Does nodejitsu have a recommended best practice? Here's the sample app I'm looking at https://github.com/madhums/nodejs-express-mongoose-demo/blob/master/config/config.example.js
17:41:31  * TooTallNatejoined
17:43:11  <mmalecki>upshoot: we recommend env variables
17:43:23  <mmalecki>or .gitignore'd config files
17:45:02  <upshoot>That's what I thought would be best practice. Still always struck me as a point of vulnerability. I may be wrong about that.
17:45:15  <upshoot>Better than putting the keys in the DB or the code it seems.
17:48:58  <mmalecki>yeah, definitely
17:49:27  <mmalecki>it's actually really safe on our infrastructure, there shouldn't be anything to worry about
17:50:01  <upshoot>One more quickie - where can I find the updated list of suppored engines that I can use in the package.json file? (would be nice if I could do >jitsu --engines to get the list..)
17:51:13  <upshoot>mmalecki, that's for the assurance re the process.env security. It's something I have not paid much attention to, but as my current app seems to have lots of keys and apis, started t to think about it more.
17:52:13  <jcrugzz>upshoot: currently we only support 0.8.x, but 0.10.x is coming soon :)
17:52:30  * defunctzombiechanged nick to defunctzombie_zz
17:52:50  <jcrugzz>well 0.8.x and 0.6.x if you dare
17:53:28  <upshoot>jcrugzz, good to know. I just found the same info in the docs: https://www.nodejitsu.com/documentation/features/#feature/multi-node but where can I learn when that changes?
17:54:00  <jcrugzz>upshoot: docs will be updated and there will be an announcement on our twitter feed for sure
17:54:33  * atomlessquit (Quit: My iMac has gone to sleep. ZZZzzz…)
17:54:38  <upshoot>Very glad to hear 10.x is coming soon, just because I'm devloping in 10.x locally, and am worried it will be a problem when I try to deploy.
17:55:09  * julianduquejoined
17:55:28  <upshoot>jcrugzz, feature request: add a cli for requesting a list of supported engines :-)
17:56:13  * joshonthewebquit (Quit: Computer has gone to sleep.)
17:56:25  <jcrugzz>upshoot: feel free to create an issue :) https://github.com/nodejitsu/jitsu/issues
17:56:59  <upshoot>cool. I'll put it it the hopper.
17:59:01  * cronopiojoined
18:10:23  * admcquit (Quit: Leaving.)
18:12:40  * atomlessjoined
18:13:02  <stevemanuel>if i'm deploying a app requiring ssl to nodejitsu, do I need to use the https module in my app? asking since I think I upload my certs to nodejitsu, not within my app..?
18:14:27  <julianduque>stevemanuel: no, you don't need https module, just create an http server and our balancers will handle the ssl for you :)
18:14:43  * RORgasmquit (Read error: Connection reset by peer)
18:14:47  <stevemanuel>got it - so nice ;) thank you
18:15:01  * RORgasmjoined
18:15:38  <julianduque>:)
18:17:08  * joshonthewebjoined
18:18:31  * jcrugzzquit (Quit: leaving)
18:19:29  * jcrugzzjoined
18:21:49  <stevemanuel>@julianduque: also, where are iriscouch Redis servers & how does upgrading work beyond 10MB free?
18:22:13  <mmalecki>stevemanuel: we can do it on demand, can you email [email protected] :-) ?
18:22:29  <mmalecki>cc me in at maciej at nodejitsu.com, we'll get you going
18:23:13  * zkirillquit (Quit: zkirill)
18:23:13  <stevemanuel>@mmalecki: sure. thank you! I don't need this done now, but I will send an intro email.. definitely anticipate needing this after I get my service deployed
18:23:42  <mmalecki>great :-)
18:23:54  <cendrizzi>Should I be using the NV location with the iris couch redis stuff
18:24:14  * c4milojoined
18:24:28  <cendrizzi>I have asked a couple of times but last night I kept getting auth errors and now my websockets which use the redis stuff seem to be very sporadic this morning
18:24:39  <cendrizzi>I wonder if it comes back to making that change last week
18:24:48  * upshootquit
18:27:42  <jcrugzz>cendrizzi: you had your redis moved to NV where your app is im guessing?
18:28:05  <cendrizzi>jcrugzz: no, how would I even do that
18:28:11  <cendrizzi>That would make sense
18:29:54  * klaemo_joined
18:30:29  <jcrugzz>cendrizzi: send an email to jason at nodejitsu.com and you can cc me jarrett at nodejitsu.com :). Are you currently on a free iris redis instance?
18:30:44  <cendrizzi>Yes I am
18:30:54  <cendrizzi>I will, thank you.
18:31:42  <jcrugzz>ok and just to clarify, this would be an upgrade of sorts (so would no longer be free) just to ensure i set the correct expectations :)
18:32:00  <jcrugzz>cendrizzi ^
18:32:47  * klaemoquit (Ping timeout: 255 seconds)
18:33:26  <cendrizzi>What is the fee?
18:33:49  <cendrizzi>And to be clear business accounts see now changes with the DB stuff?
18:34:05  <jcrugzz>cendrizzi: i am not sure honestly, the email will be the best place to start the dialogue :)
18:34:23  <cendrizzi>Okay, at this point I should probably remove redis until this is sorted out
18:34:36  <cendrizzi>It's not like I'm using more than one drone now anyway
18:34:42  <cendrizzi>Which is the only reason I enabled it
18:34:55  <cendrizzi>However I'm still using Mongo lab
18:34:58  <cendrizzi>Where are they hosted?
18:35:05  * benjaminbenbenquit (Quit: benjaminbenben)
18:35:13  <cendrizzi>I wonder if that can create issues being hosted in NV?
18:35:17  <cendrizzi>Can you confirm?
18:35:31  <cendrizzi>I might just move my stuff back to virginia
18:35:48  <jcrugzz>all of the add-ons are by default in us-east
18:35:53  <cendrizzi>Okay
18:36:12  * Hebojoined
18:36:23  <cendrizzi>I was hoping I could reduce my latency by a little more but I haven't seen much improvement so I think I'll move stuff back
18:37:12  <jcrugzz>yea it may reduce http latency (assuming you are closer to NV) but it adds latency to the database end
18:37:24  * gut4joined
18:38:27  * tobiequit (Quit: tobie)
18:39:49  * zkirilljoined
18:40:03  * fomatinquit (Quit: Computer has gone to sleep.)
18:43:45  * gut4quit (Remote host closed the connection)
18:44:03  * ed8tjoined
18:44:32  * jcrugzzquit (Ping timeout: 246 seconds)
18:46:08  * ed8t-joined
18:46:15  * jcrugzzjoined
18:47:27  * Luke_joined
18:48:21  * fomatinjoined
18:49:08  * sreeixquit (Quit: sreeix)
18:49:36  * Samuel_Roldanquit (Quit: Samuel_Roldan)
18:49:59  * ed8tquit (Ping timeout: 256 seconds)
18:51:38  * swaagie[bbl]changed nick to swaagie
18:53:13  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
18:56:20  * admcjoined
18:56:44  * Luke_quit (Quit: Page closed)
18:57:12  * Samuel_Roldanjoined
18:57:39  * jetiennejoined
18:58:02  * Heboquit
18:59:03  * thealanwattsriotjoined
18:59:52  * tobiejoined
19:02:10  * zkirillquit (Quit: zkirill)
19:03:11  * defunctzombie_zzchanged nick to defunctzombie
19:04:24  * fomatinquit (Quit: Computer has gone to sleep.)
19:04:30  * admcquit (Quit: Leaving.)
19:05:23  * zkirilljoined
19:08:57  * poormanjoined
19:12:54  * jgablequit (Quit: Computer has gone to sleep.)
19:13:00  * defunctzombiechanged nick to defunctzombie_zz
19:17:07  * atomlessquit (Quit: My iMac has gone to sleep. ZZZzzz…)
19:19:09  * bzooquit (Remote host closed the connection)
19:19:44  * bzoojoined
19:22:31  * c4miloquit (Remote host closed the connection)
19:22:43  * Hebojoined
19:24:05  * bzooquit (Ping timeout: 255 seconds)
19:27:09  * klaemo_quit (Remote host closed the connection)
19:30:05  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:32:32  * brianloveswordsquit (Max SendQ exceeded)
19:33:41  * Heboquit
19:34:11  * brianloveswordsjoined
19:34:45  * ChrisMathesonquit (Quit: ChrisMatheson)
19:34:45  * frenchtoastquit (Ping timeout: 256 seconds)
19:36:39  * bzoojoined
19:36:43  * Samuel_Roldanquit (Quit: Samuel_Roldan)
19:36:56  * jgablejoined
19:49:10  * julianduquequit (Quit: leaving)
19:50:15  * fomatinjoined
19:50:28  * jgablequit (Quit: Computer has gone to sleep.)
19:52:52  * defunctzombie_zzchanged nick to defunctzombie
19:53:11  * Hebojoined
19:58:07  * stevemanueljoined
19:58:55  * jgablejoined
20:00:32  * Samuel_Roldanjoined
20:00:36  * c4milojoined
20:12:51  * julianduquejoined
20:18:26  * defunctzombiechanged nick to defunctzombie_zz
20:20:11  * jahajoined
20:20:25  * anoemiquit (Quit: anoemi)
20:22:52  * Jester831quit (Quit: Leaving...)
20:26:59  * Heboquit
20:32:01  * Hebojoined
20:33:07  * Jester831joined
20:33:15  * Leeoljoined
20:40:08  * admcjoined
20:44:09  * Jester831quit (Quit: Leaving...)
20:46:03  * poormanquit (Read error: Operation timed out)
20:49:22  * poormanjoined
20:51:50  * c4miloquit (Remote host closed the connection)
20:53:16  * jgablequit (Quit: Computer has gone to sleep.)
20:55:33  * `3rdEdenchanged nick to `3E|Zz
21:00:06  * jgablejoined
21:01:44  * tobiequit (Ping timeout: 255 seconds)
21:01:48  * julianduquequit (Quit: leaving)
21:05:25  * generalissimoquit (Remote host closed the connection)
21:05:38  * vector_tjoined
21:07:25  * tobiejoined
21:16:52  * jxsonjoined
21:19:18  * generalissimojoined
21:22:41  * Jester831joined
21:30:31  * anoemijoined
21:31:27  * tobiequit (Quit: tobie)
21:31:32  * jgablequit (Quit: Computer has gone to sleep.)
21:33:38  * Jester831quit (Quit: Leaving...)
21:33:41  * ChrisMathesonjoined
21:34:31  * Heboquit
21:34:37  * _pantsjoined
21:34:44  * tobiejoined
21:36:23  * johnmartyquit (Ping timeout: 246 seconds)
21:36:23  <_pants>hey Sly and other jitsu folks, is there a way to suppress "jitsu deploy"'s auto-incrementing my package version? i deleted the accidentally-deployed newer versions and want a way to tell it "I know what i'm doing, please just deploy it as-is"
21:38:27  * ChrisMathesonquit (Ping timeout: 252 seconds)
21:39:37  * sirkitreechanged nick to sirkitree|afk
21:40:21  <jcrugzz>_pants: let me find that for you :)
21:40:29  <_pants>jcrugzz: thanks!
21:41:20  <_pants>jcrugzz: honestly i would even be happy to just deploy over and over to version "0.0.0" while i'm in a fast development loop. does jitsu support this?
21:41:52  <_pants>deploying on top of existing deployments is routine on other PAAS's e.g. app engine
21:42:20  <jcrugzz> _pants: well the difference is that we put your app on a new server each time you deploy
21:42:51  <jcrugzz>so the version is used to reference what one to deploy
21:43:01  <jcrugzz>but let me see something
21:43:19  <_pants>so in that case choosing the same version number can mean "use the same server and overwrite the existing deployment"
21:44:42  * Jester831joined
21:44:53  <jcrugzz>_pants: ah yes i misinterpreted your initial question. there is no way to not incremement versions
21:45:00  <jcrugzz>you must learn to love the semver
21:45:31  <jcrugzz>but you can choose to increase the patch level version automatically if youd like https://www.nodejitsu.com/documentation/jitsu/deploy/#repeated-deployments
21:46:50  <jcrugzz>_pants: so you will want to just deploy over and over until it works how you want. then just manually increase it to what you feel as the appropriate version (so its not 0.0.0-89)
21:47:10  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:47:13  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:47:13  <_pants>jcrugzz: thanks. i love semver already, just a question of what you're considering a release deployment vs. staging vs. development. other platforms don't force you to consider deploying to them some form of release (albeit even a patch release)
21:47:42  <_pants>i get the motivation behind it, just feels needlessly controlling
21:48:10  <jcrugzz>_pants: well to me anything 0.0.0-x is a meaningless version
21:48:19  <jcrugzz>or even 0.1.0-x
21:48:33  <_pants>jcrugzz: well, so why burden everyone with managing them as separate versions
21:48:45  <_pants>"i really do want to overwrite this version, please let me"
21:49:06  <jcrugzz>what makes it a burden?
21:49:12  <jcrugzz>out of curiosity
21:49:21  * vector_tquit (Ping timeout: 248 seconds)
21:49:40  <_pants>having cruft accumulate
21:50:08  <_pants>that is (as you already said) not meaningful
21:51:03  <_pants>jcrugzz: can you just kill all extant deployments of my app with fire please, so i'll be allowed to redeploy a lower version?
21:51:08  <_pants>app id lantern-ui
21:51:22  <jcrugzz>well what it allows for is a record of all of your snapshots (if they happen to be useful)
21:51:46  <_pants>right, i appreciate that, just suggesting "allowing for" > "forcing"
21:52:06  <_pants>i'll open a ticket if you're open to reconsideration
21:53:17  <jcrugzz>_pants: yea i understand. My recommendation for the time being is to just test locally thoroughly and not deploy until it isnt 'cruft' :).
21:53:27  <jcrugzz>and add your suggestion to nodejitsu.uservoice.com
21:53:40  <_pants>jcrugzz: not possible when i need to point other people at it not in the same room
21:54:06  <_pants>jcrugzz: can you nuke all my existing deployed versions?
21:54:21  <jcrugzz>_pants: username?
21:54:27  <_pants>lantern
21:54:36  <_pants>(thank you!)
21:55:23  * RORgasmquit (Read error: Connection reset by peer)
21:55:41  * RORgasmjoined
21:57:29  <jcrugzz>_pants: you should be clean now.
21:58:20  <_pants>jcrugzz: thank you! i see https://webops.nodejitsu.com/apps/lantern-ui shows nothing under the snapshots tab, but still says "active snapshot: 0.1.0-4"
21:58:49  <_pants>jcrugzz: and sure enough, "jitsu deploy" still tries to rewrite my local package.json with a bumped version
21:59:45  <jcrugzz>_pants: yes we cannot delete your running app, and yes it will still continue to do this. I just cleaned up your snapshot references.
22:00:59  <jcrugzz>the incrementing of versions will still be part of how our architecture works
22:01:09  * chrisdotcodejoined
22:01:26  <_pants>jcrugzz: oh, the thing i'm trying to do is deploy with a lower version. can you just kill everything with fire so it doesn't think there is a higher version deployed already?
22:01:43  <jcrugzz>_pants: do a jitsu destroy and recreate the app
22:02:10  <_pants>jcrugzz: ok, thanks. that won't lose any free open source drone status or anything?
22:02:55  <jcrugzz>_pants: that may complicate things. i would hold off on the destroy.
22:03:32  <_pants>so is there anything else we can do? can you change the version of the snapshot it thinks is currently-deployed to 0.0.0?
22:04:08  <jcrugzz>_pants: no im sorry. it can only be a higher version
22:05:04  <_pants>nazijitsu
22:05:27  <_pants>ok, i'll file a ticket. thanks for trying.
22:05:57  <jcrugzz>haha, you still control the versions, they just need to logically increase in some way :)
22:06:03  * Jester831quit (Quit: Leaving...)
22:06:09  <jcrugzz>but yea im sry i cant do anything more
22:06:18  <_pants>this is very accident-hostile
22:08:48  <jcrugzz>_pants: O.o in what way?
22:10:12  <_pants>https://github.com/nodejitsu/jitsu/issues/450
22:10:18  <_pants>jcrugzz: ^
22:12:43  <_pants>jcrugzz: so just to make sure, there's *nothing* you can do to make things sane for me again? i'm forced to bump back up to the bogus version and use that forevermore if i ever want to deploy to nodejitsu again?
22:12:45  * InconceivableBquit (Ping timeout: 246 seconds)
22:13:06  * tobiequit (Ping timeout: 246 seconds)
22:13:19  * stevemanueljoined
22:14:45  * tobiejoined
22:15:43  * InconceivableBjoined
22:16:24  <jcrugzz>_pants: there is no easy way to get you back on the open source drone if its destroyed :/. Submit a ticket to [email protected], ill talk with julianduque who is in charge of the open source assignments
22:16:47  <_pants>jcrugzz: ok, will do, thanks
22:19:40  * tobiequit (Quit: tobie)
22:22:25  * sirkitree|afkquit (Ping timeout: 248 seconds)
22:23:41  * Samuel_Roldan_joined
22:25:25  * Samuel_Roldan_quit (Client Quit)
22:25:48  * generalissimoquit (Remote host closed the connection)
22:26:47  * Samuel_Roldanquit (Ping timeout: 255 seconds)
22:34:02  * Hebojoined
22:35:07  * Jester831joined
22:37:43  * ed8t-quit (Ping timeout: 264 seconds)
22:37:46  * c4milojoined
22:40:00  * xobxobjoined
22:42:38  <xobxob>Hi. Is there a way to support multiple sub-domains from one app on nodejitsu (for example, api.blah.com and dashboard.blah.com using the same app)?
22:42:43  * leichtgewichtquit (Remote host closed the connection)
22:42:49  * _pantspart
22:43:11  * leichtgewichtjoined
22:44:00  <jcrugzz>xobxob: yes for your own custom domain you can even do, *.customDomain.com
22:44:13  <jcrugzz>assuming your dns is setup properly of course :)
22:45:10  <xobxob>So, I just need to forward sub-domain requests properly. Then I can test from the app what domain the request was sent to?
22:47:56  * leichtgewichtquit (Ping timeout: 255 seconds)
22:48:20  <jcrugzz>xobxob: yea exactly
22:49:33  <jcrugzz>a decent example that shows URL detection is https://www.nodejitsu.com/documentation/faq/#how-do-i-force-my-clients-to-use-https-with-my-application
22:52:23  * erichoceanjoined
22:54:29  <xobxob>jcrugzz: perfect. thanks for your help!
22:54:39  <jcrugzz>no problem!
22:55:18  * RORgasmquit (Read error: Connection reset by peer)
22:55:34  * RORgasmjoined
23:01:55  * xobxobpart
23:02:14  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
23:04:07  * rcombsquit (Ping timeout: 264 seconds)
23:14:50  * jgablejoined
23:21:44  * julianduquejoined
23:27:24  * rombquit (Ping timeout: 240 seconds)
23:28:55  * marfarma__joined
23:29:30  * marfarmaquit (Ping timeout: 264 seconds)
23:29:31  * marfarma__changed nick to marfarma
23:31:19  * c4milo_joined
23:31:40  * joshonthewebquit (Quit: Computer has gone to sleep.)
23:31:59  * c4milo_quit (Remote host closed the connection)
23:32:16  * c4milo_joined
23:32:18  * mdedetrichjoined
23:34:36  * RORgasm_joined
23:34:46  * RORgasmquit (Read error: Connection reset by peer)
23:36:27  * jgablequit (Quit: Computer has gone to sleep.)
23:37:15  * zz_rombjoined
23:37:19  * zz_rombchanged nick to romb
23:37:20  * rombquit (Changing host)
23:37:21  * rombjoined
23:39:21  * c4milo_quit (Remote host closed the connection)
23:41:36  * Heboquit
23:44:33  * ChrisMathesonjoined
23:47:41  * Hebojoined
23:49:21  * ChrisMathesonquit (Ping timeout: 252 seconds)
23:50:25  * rombquit (Ping timeout: 248 seconds)
23:50:46  * jgablejoined
23:50:47  * fomatinquit (Quit: Computer has gone to sleep.)
23:52:53  * erichoceanquit (Quit: erichocean)
23:54:18  * Samuel_Roldanjoined
23:58:14  * admcquit (Quit: Leaving.)