00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:09  * ircretaryjoined
00:00:15  * Fishrock123joined
00:03:57  <nathan7>distilledchaos: Your app is up from every balancer [=
00:04:44  <grownseed>... and now i'm looking into implementing my own load balancer instead of doing my job... you guys should feel terrible about yourselves! :P
00:04:51  * Fishrock123quit (Ping timeout: 260 seconds)
00:05:29  <nathan7>grownseed: I just beat three load balancers into submission! Hah!
00:05:33  * generalissimojoined
00:05:37  <distilledchaos>nathan7: YAY
00:05:54  <distilledchaos>nathan7: YOU ARE A GOD
00:05:56  <jcrugzz>distilledchaos: i told you it would get done :)
00:06:08  <grownseed>"treat your balancers like your women" as they often say...
00:06:27  * kenperkinsquit (Quit: Textual IRC Client: http://www.textualapp.com/)
00:06:31  <nathan7>grownseed: keep great distance?
00:06:54  * kperchquit (Remote host closed the connection)
00:06:59  * araljoined
00:08:10  <distilledchaos>jcrugzz: very true
00:08:20  <nathan7>Good night, earthlings
00:08:23  <nathan7>Enjoy your apps q=
00:08:40  <distilledchaos>I SHALL
00:08:58  <grownseed>nathan7: night night, no funny business with the other balancers you chicky you
00:09:19  <aral>Hey, quick question: does anyone know if the business plans are affected too? Thinking it might be worthwhile to shell out for one of those.
00:13:20  <jcrugzz>aral: business plans were also affected by the issues the past couple days. While they do provide their advantages, id advise to wait a couple days while the last kinks are worked out :)
00:13:29  * indexzerojoined
00:14:10  <aral>@jcrugzz Thanks, will do :)
00:14:36  <aral>Darn thing is, I *love* the approach & workflow of the company. Will hang in there.
00:15:04  <jcrugzz>aral: i know the feeling :)
00:15:48  <grownseed>Ladies, Gents, catch you later!
00:16:08  <R_Macy>Why is redistogo disabled, just curious
00:16:12  <jcrugzz>grownseed: later
00:16:56  <aral>’night ’night, folks, may all your sites be your own sites tomorrow :)
00:17:00  <distilledchaos>R_Macy: i'm curious, too, it's been that way for months
00:17:06  <distilledchaos>haha
00:17:43  * aralquit (Quit: aral)
00:18:12  <R_Macy>distilledchaos odd :-)
00:18:38  <R_Macy>also, is the database interface up? I've tried creating a mongohq instance 3 times already
00:18:42  <R_Macy>it just seems to hang
00:18:46  <distilledchaos>i've some bad news
00:19:01  <distilledchaos>it's still not up for some of my users, nathan7
00:19:20  <distilledchaos>same ECONNREFUSED error
00:19:32  <jcrugzz>distilledchaos: he went off to bed. and thats odd. have them shift refresh
00:19:38  <jcrugzz>it may be cached
00:19:58  <R_Macy>mongolab worked
00:20:03  * grownseedquit (Ping timeout: 245 seconds)
00:20:05  <R_Macy>:/
00:22:00  <blakmatrix>R_Macy: a few months ago something happened with their provisioning service that caused spotty service, so we put it on the back burner, I believe you can still try provisionin it in jitsu however
00:22:00  <distilledchaos>same problem
00:22:31  * Samuel_Roldanquit (Quit: Samuel_Roldan)
00:22:38  * Fishrock123joined
00:22:46  <R_Macy>blakmatrix Ok, thanks for the heads up
00:23:56  <distilledchaos>jcrugzz: after trying clearing cache, opening in private browsing window, etc...it still doesn't work
00:24:04  <distilledchaos>jcrugzz: and yet...trying a raw telnet request on port 80 works
00:24:10  * Domenic_joined
00:24:11  <distilledchaos>i get the expected response
00:24:13  <distilledchaos>so...
00:24:18  <distilledchaos>i don't know >.<
00:24:56  <jcrugzz>distilledchaos: O.o hold on
00:24:59  <distilledchaos>ok
00:25:51  <distilledchaos>it's working for one of my users now
00:25:57  <distilledchaos>but not anybody else
00:27:18  <jcrugzz>they get the same econnrefused?
00:27:29  * kperchjoined
00:28:20  * Fishrock123quit (Remote host closed the connection)
00:28:27  * slloydquit (Quit: Leaving...)
00:28:40  * Domenic_quit (Ping timeout: 250 seconds)
00:29:38  * admc1changed nick to admc
00:30:33  <distilledchaos>jcrugzz: yes
00:30:38  <distilledchaos>it's always the same error
00:30:46  * robmozartquit (Remote host closed the connection)
00:33:20  <blakmatrix>distilledchaos: can you step me through what you're seeing,
00:35:56  * marcello3dquit (Remote host closed the connection)
00:41:25  <blakmatrix>distilledchaos: does the silence mean everything is ok now ?
00:47:26  * R_Macyquit (Quit: Computer has gone to sleep.)
00:48:07  * papachanquit (Quit: Saliendo)
00:49:07  * bradleymeckjoined
00:50:02  <zarac>Haha, nodejitsu does PaaS. I had no clue. ; )
00:50:31  <zarac>I came here through docs.nodejitsu.com ;)
00:50:56  <jcrugzz>zarac: awesome way to come across the channel !
00:51:18  * porsagerquit (Ping timeout: 245 seconds)
00:51:56  <zarac>: )
00:52:23  * bradleymeckquit (Client Quit)
00:53:19  * jcrugzzchanged nick to jcrugzz|food
00:58:30  <distilledchaos>blakmatrix: sorry about that...it started working and i was needed elsewhere
00:58:31  <distilledchaos>but yes
00:58:35  <distilledchaos>it appears to be working now
00:58:45  <distilledchaos>hopefully permanently
01:09:39  * jcrugzz|foodchanged nick to jcrugzz
01:12:52  * Murray_joined
01:13:27  * anoemiquit (Quit: anoemi)
01:13:44  <Murray_>Quick question: do Nodejitsu's load balancers have any preference for sending the same IP back to the same node for each request? or is it entirely random?
01:14:08  <blakmatrix>Murray_: we have sticky sessions yes
01:14:27  <Sly>Murray_: the balancers are on round-robin. They'll auto rotate in browsers.
01:14:43  <Sly>If you want to target one, use `curl <ip> -H "Host: yourdomain.jit.su"`
01:14:51  <Murray_>fantastic! just designing a local caching system for our nodes and that will make things a lot easier
01:15:16  * kimpettersenjoined
01:15:24  <Murray_>thanks very much
01:25:46  * kperchquit (Remote host closed the connection)
01:26:43  * marcello3djoined
01:28:24  * lresendejoined
01:37:40  * inspironquit (Quit: Page closed)
01:39:04  * marcello3dquit (Remote host closed the connection)
01:40:03  * pedrodiasjoined
01:40:27  * Domenic_joined
01:40:42  * distilledchaosquit (Read error: Connection reset by peer)
01:45:44  * lresendequit (Quit: lresende)
01:47:59  * lresendejoined
01:53:47  * kimpettersenquit (Ping timeout: 245 seconds)
01:55:03  * Murray_quit (Ping timeout: 245 seconds)
01:56:07  * jlankjoined
02:07:26  * generalissimoquit (Remote host closed the connection)
02:11:12  * Nodejitsu-Githubjoined
02:11:12  <Nodejitsu-Github>[godot] jcrugzz opened pull request #37: Added new `By` reactor (master...by-reactor) http://git.io/Pl26tQ
02:11:12  * Nodejitsu-Githubpart
02:11:29  * DTrejoquit (Remote host closed the connection)
02:12:23  * gouldingjoined
02:16:05  * blakmatrixquit (Remote host closed the connection)
02:16:21  * jcrugzzquit (Ping timeout: 257 seconds)
02:16:25  <goulding>I see that errors.jit.su is returning either ECONNREFUSED or ECONNRESET. I haven't been getting this error message as much as in the past, but its very disappointing that it is still there
02:17:31  * Murray_joined
02:18:21  * distilledchaosjoined
02:18:32  <Murray_>sorry guys one extra question, is there a preferred way to give outside access to an additional port on our nodes? Will be using it for profiling access in our staging node, and currently planning on using the http-proxy module, but wondered if there is a better way
02:20:01  <goulding>I'm trying to decide whether to go with one of the business plans, but I can't justify that kind of $$ unless I can be sure the ECONNRESET thing is sorted out
02:21:14  * faceleg|sleepjoined
02:23:26  * lresendequit (Quit: Zzzzzzz ...)
02:25:40  * faceleg|sleepquit (Ping timeout: 250 seconds)
02:26:06  <distilledchaos>blakmatrix: jcrugzz: one user is reporting that one static file is still reporting the same error
02:30:33  * YoYjoined
02:35:02  * jcrugzzjoined
02:36:23  * kperchjoined
02:36:43  * ramitosquit
02:40:43  <distilledchaos>no?
02:41:00  * kperchquit (Ping timeout: 260 seconds)
02:41:43  * Murray_quit (Ping timeout: 245 seconds)
02:42:05  <jcrugzz>distilledchaos: whats up?
02:42:14  <distilledchaos>one user is reporting that one static file is still reporting the same error
02:42:21  <jcrugzz>hmm, let me see
02:42:21  * indexzeroquit (Quit: indexzero)
02:42:24  <distilledchaos>we tried clearing the cache
02:42:27  <distilledchaos>but that didn't work
02:44:58  * indexzerojoined
02:45:08  * Samuel_Roldanjoined
02:46:10  * ChaoticJorgequit (Quit: Computer has gone to sleep.)
02:51:05  * admcquit (Quit: Leaving.)
02:51:14  <zarac>In case anyone cares; I ended up using xml2js. ; )
02:51:25  * BrandonGriggspart
02:51:48  * YoYquit (Quit: Computer has gone to sleep.)
02:52:10  * admcjoined
02:53:14  <jcrugzz>distilledchaos what is the app name?
02:54:44  * thirdjoined
02:55:34  * gouldingquit (Quit: Page closed)
02:56:43  * thl0joined
02:58:32  * YoYjoined
02:58:49  <jcrugzz>distilledchaos: and its being looked into, seems like an LB is being a bit of an issue
03:08:03  * DTrejojoined
03:09:42  * TooTallNatequit (Quit: Computer has gone to sleep.)
03:09:56  * YoYquit (Quit: Computer has gone to sleep.)
03:10:26  * anoemijoined
03:12:38  * YoYjoined
03:16:30  <third>hi, how do you configure wildcard SSL with Nodejitsu?
03:17:49  <jcrugzz>third: is this for your own domain?
03:18:01  <third>yes
03:18:28  * Heboquit
03:18:43  <jcrugzz>third do you have a business plan?
03:18:59  <third>I have a personal plan right now
03:20:27  <jcrugzz>third: SSL for custom domains are only enabled for business plans. On individual plans you can get SSL automatically on the *.jit.su domains
03:20:32  <distilledchaos>jcrugzz: also, sorry for the repeated afks, now that it's working, we're trying to analyze a lot of data
03:20:56  <jcrugzz>distilledchaos: its all good, was going to let you know that it was resolved :)
03:21:07  * c4milojoined
03:23:47  * admcquit (Quit: Leaving.)
03:26:40  <third>jcrugzz: really, only business plan offer custom SSL?
03:30:23  <jcrugzz>third: yes, the individual plans are the basic plans essentially.
03:31:39  * c4miloquit (Remote host closed the connection)
03:32:50  * mbalhojoined
03:33:34  <mbalho>can someone help me figure out why my deploys arent working? I get "Rackspace Error (404): Item not found"
03:34:24  <jcrugzz>mbalho: can you run a `jitsu deploy --debug` and pm me the gist of the output?
03:35:09  * c4milojoined
03:35:12  <third>jcrugzz: do you know if you are allowed to have a mix of individual plan and business plan? Or do I have to open another account? I'm planning to upgrade just one of my app to business plan and keep the rest on individual plan while our business is just starting up.
03:36:04  <jcrugzz>third: for now I believe you would just create a new account. One for business, one for individual
03:36:31  <mbalho>jcrugzz: oh NVM did it again and it worked
03:36:59  <jcrugzz>mbalho: ok cool :)
03:38:10  <distilledchaos>mbalho: it's great when that happens, but also frustrating because you don't know if it was something you did
03:39:40  * YoYquit (Quit: Computer has gone to sleep.)
03:40:38  <jcrugzz>distilledchaos: it is unfortunate, but I do not forsee this for too much longer.
03:41:01  * Nodejitsu-Githubjoined
03:41:01  <Nodejitsu-Github>[godot] indexzero created gh-36 (+4 new commits): http://git.io/6QSFww
03:41:01  <Nodejitsu-Github>godot/gh-36 96e5b34 Jarrett Cruger: Added new by reactor
03:41:01  <Nodejitsu-Github>godot/gh-36 fb135c7 Jarrett Cruger: Added By reactor to array to be registered
03:41:01  <Nodejitsu-Github>godot/gh-36 a3367ea Jarrett Cruger: Added error checking when instantiated, emits data regardless to allow it to still be chainable.
03:41:01  * Nodejitsu-Githubpart
03:41:24  <distilledchaos>jcrugzz: yay :D
03:41:52  * Nodejitsu-Githubjoined
03:41:52  <Nodejitsu-Github>[godot] indexzero opened pull request #38: Added .by() (master...gh-36) http://git.io/3w91AA
03:41:52  * Nodejitsu-Githubpart
03:43:05  <jcrugzz>haha thanks.
03:43:30  <third>jcrugzz: is there minimum number of drone to subscribe for business plan?
03:43:53  <jcrugzz>third: lowest plan is 2 i believe
03:45:33  * Nodejitsu-Githubjoined
03:45:33  <Nodejitsu-Github>[godot] indexzero pushed 1 new commit to gh-36: http://git.io/DcO0Dw
03:45:33  <Nodejitsu-Github>godot/gh-36 6b03a94 indexzero: [test] Test `.by(Array, reactor)`.
03:45:33  * Nodejitsu-Githubpart
03:45:35  * joshonthewebjoined
03:46:06  * Nodejitsu-Githubjoined
03:46:06  <Nodejitsu-Github>[godot] indexzero deleted gh-36 at 6b03a94: http://git.io/326pmQ
03:46:06  * Nodejitsu-Githubpart
03:46:46  <third>jcrugzz: do you know why at least 2? Say if I only have 1 app, why pay for 2?
03:47:24  <indexzero>third: Most business apps are using at least two drones
03:50:46  * generalissimojoined
03:54:37  * mbalhopart
04:02:19  * z0w0quit (Read error: Connection reset by peer)
04:03:31  <third>indexzero: does the business plan offer staging deployment of app?
04:03:58  <indexzero>third: If you're using one drone, you can have two versions of your app, one as "staging"
04:04:01  <indexzero>e.g. app and app-staging
04:04:16  * bardupart
04:05:08  <third>indexzero: yes, I do that on individual plan. I'm just curious if it's different on business plan. Now it make sense why the need of at least 2 drones.
04:05:58  <indexzero>it's not different, but business plans have configurable drone sizes (e.g. 512MB). It did not make sense to have a business plan that could not use this feature
04:13:36  * Nodejitsu-Githubjoined
04:13:36  <Nodejitsu-Github>[godot] indexzero created feature-thru (+1 new commit): http://git.io/X24bxg
04:13:36  <Nodejitsu-Github>godot/feature-thru 3fb47e7 indexzero: [api test] Added `.thru()` for piping to multiple independent reactors.
04:13:36  * Nodejitsu-Githubpart
04:14:45  * switzjoined
04:14:49  * switzquit (Client Quit)
04:18:36  * marcello3djoined
04:19:00  * TooTallNatejoined
04:19:09  * Nodejitsu-Githubjoined
04:19:09  <Nodejitsu-Github>[godot] indexzero pushed 1 new commit to feature-thru: http://git.io/d3D4fw
04:19:09  <Nodejitsu-Github>godot/feature-thru f66656f indexzero: [test] Added test for cannonical `thru` example: react to `.over()` and `.under()` independently.
04:19:09  * Nodejitsu-Githubpart
04:21:05  * Nijikoquit (Quit: Computer has gone to sleep.)
04:21:34  * Nodejitsu-Githubjoined
04:21:34  <Nodejitsu-Github>[godot] indexzero opened pull request #39: React to different criteria independently with `.thru()` (master...feature-thru) http://git.io/0Hx1zw
04:21:34  * Nodejitsu-Githubpart
04:21:54  * Nodejitsu-Githubjoined
04:21:54  <Nodejitsu-Github>[godot] indexzero deleted feature-thru at f66656f: http://git.io/QMD0YA
04:21:54  * Nodejitsu-Githubpart
04:22:07  * Nijikojoined
04:23:03  * st_lukejoined
04:26:03  * YoYjoined
04:26:54  * Nodejitsu-Githubjoined
04:26:54  <Nodejitsu-Github>[godot] indexzero pushed 3 new commits to master: http://git.io/szvWpg
04:26:54  <Nodejitsu-Github>godot/master 1b258d8 Jarrett Cruger: Added ability to listen on unix sockets
04:26:54  <Nodejitsu-Github>godot/master c38c6fd Jarrett Cruger: Added tests for listening on unix socket
04:26:54  <Nodejitsu-Github>godot/master cc07a25 Jarrett Cruger: [fix] Renamed test macros to make sense for more than 2 types of connections
04:26:54  * Nodejitsu-Githubpart
04:27:55  * Nijikoquit (Quit: Textual IRC Client: www.textualapp.com)
04:28:45  * Nodejitsu-Githubjoined
04:28:46  <Nodejitsu-Github>[godot] indexzero pushed 1 new commit to master: http://git.io/Os3YSQ
04:28:46  <Nodejitsu-Github>godot/master 34278ca indexzero: [dist] Version bump. 0.3.0
04:28:46  * Nodejitsu-Githubpart
04:28:53  * sreeixjoined
04:29:33  * sreeixquit (Client Quit)
04:37:15  * DTrejoquit (Remote host closed the connection)
04:38:12  * R_Macy_joined
04:47:44  * YoYquit (Quit: Computer has gone to sleep.)
04:49:09  * thl0quit (Remote host closed the connection)
04:49:22  * Nodejitsu-Githubjoined
04:49:22  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 3 new commits to master: http://git.io/bSSdcA
04:49:22  <Nodejitsu-Github>node-http-proxy/master ee6bbe0 jamie-stackhouse: Change wording for handling websocket proxy events
04:49:22  <Nodejitsu-Github>node-http-proxy/master 603106a jamie-stackhouse: Re-added previous description
04:49:22  <Nodejitsu-Github>node-http-proxy/master c686ac7 Charlie Robbins: Merge pull request #349 from jamie-stackhouse/patch-1...
04:49:22  * Nodejitsu-Githubpart
04:49:47  <fusiongrokker>anyone here using nano for couchdb and doing bulk deletes? trying to figure out what I'm doing wrong...
04:51:02  * travis-cijoined
04:51:02  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#106 (master - c686ac7 : Charlie Robbins): The build passed.
04:51:02  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/26d3646ff252...c686ac7b0145
04:51:02  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5360781
04:51:02  * travis-cipart
04:51:22  * thirdquit (Quit: Page closed)
04:52:07  * blakmatrixjoined
04:52:15  <jcrugzz>fusiongrokker: I can try and help you. show me what you have
04:52:27  <fusiongrokker>sure, let me put it in a gist
04:52:28  <fusiongrokker>thanks
04:53:48  <jcrugzz>np
04:55:15  <fusiongrokker>https://gist.github.com/atuttle/a57be3663d2baaed24a3
04:57:52  * marcello3dquit (Remote host closed the connection)
04:58:01  * motiooon_joined
04:58:14  * motiooon_quit (Client Quit)
04:58:19  <jcrugzz>fusiongrokker: you are passing in an array, it wants a { "docs": [] }
04:58:21  * marcello3djoined
04:58:27  <jcrugzz>so if you wrap it with that I think it will work
04:58:28  <fusiongrokker>ah
04:58:30  <fusiongrokker>thanks
04:58:33  <jcrugzz>np
04:59:19  <fusiongrokker>perfect!
04:59:21  <fusiongrokker>hooray!
04:59:30  <fusiongrokker>now I can stop making 12k requests to delete 12k records.
04:59:43  <fusiongrokker>\o/
05:00:34  <jcrugzz>fusiongrokker: good work!
05:00:51  <fusiongrokker>jcrugzz: same to you, fella!
05:01:53  <jcrugzz>fusiongrokker: no problem, its always the little things that sneak up on you
05:01:59  <fusiongrokker>quite.
05:02:37  * marcello3dquit (Ping timeout: 240 seconds)
05:03:22  <fusiongrokker>ironically, I've been planning for (inevitable) career day at my kids school, where I'll go in and do a programming demonstration by having a kid blindfolded and have them give me instructions on how to make a PB&J sandwich, and interpret their directions as literally as possible... "put the peanut butter on the bread" => pick up jar, place on loaf... etc. :)
05:04:57  <jcrugzz>thats awesome. lesson in logic :)
05:06:49  * c4milo_joined
05:07:10  * c4miloquit (Read error: Connection reset by peer)
05:09:32  * blakmatrixquit (Remote host closed the connection)
05:09:34  * sreeixjoined
05:10:19  * sreeixquit (Client Quit)
05:10:41  * drewwwquit (Quit: drewww)
05:12:13  * Nodejitsu-Githubjoined
05:12:13  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 3 new commits to master: http://git.io/x6xIbw
05:12:13  <Nodejitsu-Github>node-http-proxy/master 43e5f33 Giannis Dzegoutanis: fixed issue #364 'proxyError' event emitted twice
05:12:13  <Nodejitsu-Github>node-http-proxy/master 3b84e27 Giannis Dzegoutanis: remove offending code, final fix for issue #364
05:12:13  <Nodejitsu-Github>node-http-proxy/master 8b38c99 Charlie Robbins: Merge pull request #374 from erasmospunk/master...
05:12:13  * Nodejitsu-Githubpart
05:13:59  * travis-cijoined
05:13:59  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#107 (master - 8b38c99 : Charlie Robbins): The build passed.
05:13:59  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/c686ac7b0145...8b38c994a9f9
05:13:59  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5360905
05:13:59  * travis-cipart
05:14:33  * Nodejitsu-Githubjoined
05:14:33  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/mP7Ipg
05:14:33  <Nodejitsu-Github>node-http-proxy/master 15afc23 Anders Johnson: fix 'this' reference in routing proxy listener bindings
05:14:33  <Nodejitsu-Github>node-http-proxy/master 025adc2 Charlie Robbins: Merge pull request #365 from adjohnson916/master...
05:14:33  * Nodejitsu-Githubpart
05:16:14  * travis-cijoined
05:16:14  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#108 (master - 025adc2 : Charlie Robbins): The build passed.
05:16:14  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/8b38c994a9f9...025adc29123e
05:16:14  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5360916
05:16:14  * travis-cipart
05:20:31  * st_lukequit (Read error: Connection reset by peer)
05:21:11  * Nodejitsu-Githubjoined
05:21:11  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 5 new commits to master: http://git.io/_sISZQ
05:21:11  <Nodejitsu-Github>node-http-proxy/master 916d44e Otávio Ribeiro: Routing Proxy was not sending x-forward-*. Fixing It...
05:21:11  <Nodejitsu-Github>node-http-proxy/master 1332409 Otávio Ribeiro: working on x-forwarded-for
05:21:11  <Nodejitsu-Github>node-http-proxy/master 31fc94a Otávio Ribeiro: working on x-forwarded-for
05:21:11  * Nodejitsu-Githubpart
05:22:54  * travis-cijoined
05:22:54  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#109 (master - 9672b99 : Otávio Ribeiro): The build passed.
05:22:54  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/025adc29123e...9672b9927156
05:22:54  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5360971
05:22:54  * travis-cipart
05:24:24  * Nodejitsu-Githubjoined
05:24:24  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 3 new commits to master: http://git.io/O4Aviw
05:24:24  <Nodejitsu-Github>node-http-proxy/master 83fbd42 Oscar Östlund: Added simple round robin example with websocket support
05:24:24  <Nodejitsu-Github>node-http-proxy/master 64efa7f Oscar Östlund: Added comments
05:24:24  <Nodejitsu-Github>node-http-proxy/master deca756 indexzero: [doc fix] Add undefined var in example.
05:24:24  * Nodejitsu-Githubpart
05:26:04  * travis-cijoined
05:26:04  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#110 (master - deca756 : indexzero): The build passed.
05:26:04  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/9672b9927156...deca7565c51f
05:26:04  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5360986
05:26:04  * travis-cipart
05:28:48  * sreeixjoined
05:29:14  * Nodejitsu-Githubjoined
05:29:15  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/xPtx9w
05:29:15  <Nodejitsu-Github>node-http-proxy/master 013cb2e indexzero: [fix] Ensure `response.headers.location` is defined. Fixes #276.
05:29:15  * Nodejitsu-Githubpart
05:30:53  * travis-cijoined
05:30:53  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#111 (master - 013cb2e : indexzero): The build passed.
05:30:53  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/deca7565c51f...013cb2e0c208
05:30:53  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361010
05:30:53  * travis-cipart
05:34:03  <fusiongrokker>is there a reason that jitsu keeps build tarballs in ~/.jitsu indefinitely? or safe to clear it out once in a while?
05:35:33  * sreeixquit (Quit: sreeix)
05:39:26  <jcrugzz>fusiongrokker: not sure actually. i dont think it would hurt if you deleted them
05:39:36  <jcrugzz>you can always fetch them again
05:39:44  <jcrugzz>if ever needed
05:39:54  * maasanjoined
05:40:15  <fusiongrokker>just bugs me that deploying 2 apps ~10 times a day results in 20 tarballs per day...
05:40:22  * Nodejitsu-Githubjoined
05:40:22  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/3g86MA
05:40:22  <Nodejitsu-Github>node-http-proxy/master 2055d0c unknown: memory leak fix in closing of the scokets
05:40:22  <Nodejitsu-Github>node-http-proxy/master a681493 indexzero: [fix minor] Prevent crashes from attempting to remove listeners more than once when proxying websocket requests.
05:40:22  * Nodejitsu-Githubpart
05:40:28  * anoemiquit (Quit: anoemi)
05:40:31  * SunnyShahjoined
05:41:53  <jcrugzz>fusiongrokker: you could post something on github issues about jitsu. cleanup command of sorts maybe?
05:42:24  <fusiongrokker>perhaps. or better: just keep last N, so you're always deleting the oldest 1 once you reach N.
05:42:25  * travis-cijoined
05:42:26  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#112 (master - a681493 : indexzero): The build passed.
05:42:26  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/013cb2e0c208...a681493371ae
05:42:26  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361105
05:42:26  * travis-cipart
05:44:03  <maasan>can you anyone share jitsu bash aliases
05:44:19  * Nodejitsu-Githubjoined
05:44:19  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/lnEOPw
05:44:19  <Nodejitsu-Github>node-http-proxy/master c6da760 indexzero: Revert "[fix minor] Prevent crashes from attempting to remove listeners more than once when proxying websocket requests."...
05:44:19  * Nodejitsu-Githubpart
05:45:11  * Samuel_Roldanquit (Quit: Samuel_Roldan)
05:45:43  * travis-cijoined
05:45:43  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#113 (master - c6da760 : indexzero): The build passed.
05:45:43  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/a681493371ae...c6da760ca9f3
05:45:43  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361131
05:45:43  * travis-cipart
05:45:48  * Nodejitsu-Githubjoined
05:45:48  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/_MkwtA
05:45:48  <Nodejitsu-Github>node-http-proxy/master 03dbe11 Sérgio Ramos: add "with custom server logic" to the "Proxying WebSockets" section of the readme.md
05:45:48  <Nodejitsu-Github>node-http-proxy/master eee6bab Charlie Robbins: Merge pull request #332 from ramitos/patch-1...
05:45:48  * Nodejitsu-Githubpart
05:45:50  <fusiongrokker>maasan: I don't understand what you're asking...
05:48:04  <maasan>fusiongrokker: I am using bash_it with my Terminal. It has wonderful aliases for git, heroku. But i could not find any useful bash aliases for jitsu
05:48:58  <fusiongrokker>hm, I hadn't thought of creating any; it's relatively simple as-is.
05:50:51  <maasan>fusiongrokker: Yes, it is simple to write. Before writing, if i want to figure out if anyone already written it like bash_it aliases
05:51:26  <fusiongrokker>maasan: no, I meant that the jitsu tool itself is simple -- I don't see the need for aliases.
05:52:13  * Samuel_Roldanjoined
05:52:26  <maasan>fusiongrokker: i dont want to jitsu deploy everytime, i like to type 'jd'. similarly other commands
05:52:48  <fusiongrokker>ok, go for it. :)
06:05:48  * c4milo_quit (Remote host closed the connection)
06:05:48  * SunnyShahquit (Quit: Leaving)
06:05:52  * Nodejitsu-Githubjoined
06:05:52  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/tsy2oQ
06:05:52  <Nodejitsu-Github>node-http-proxy/master ffe74ed Yosef Dinerstein: - support unix donain sockets and windows named pipes (socketPath) on node 0.8.x. On node 0.6.x the support was opaque via port, but on the new node, socketPath should be set explicitely....
06:05:52  <Nodejitsu-Github>node-http-proxy/master ecb5472 Gilad Oren: Add tests for headers bug fixes
06:05:52  * Nodejitsu-Githubpart
06:07:36  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
06:07:39  * travis-cijoined
06:07:39  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#115 (master - ecb5472 : Gilad Oren): The build passed.
06:07:39  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/eee6babc98b9...ecb547223f3f
06:07:39  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361279
06:07:39  * travis-cipart
06:10:27  * Nodejitsu-Githubjoined
06:10:27  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/hpam7A
06:10:27  <Nodejitsu-Github>node-http-proxy/master 28a3b0a indexzero: [fix] Remove special case handling of `304` responses since it was fixed in 182dcd3. Fixes #322.
06:10:27  * Nodejitsu-Githubpart
06:11:54  * Nodejitsu-Githubjoined
06:11:54  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/30KNtw
06:11:54  <Nodejitsu-Github>node-http-proxy/master 850171c Tomaz Muraus: If HTTP 1.1 is used and backend doesn't return 'Connection' header, explicitly...
06:11:54  <Nodejitsu-Github>node-http-proxy/master af9eb06 Charlie Robbins: Merge pull request #298 from Kami/connection_keep_alive_on_1_1...
06:11:54  * Nodejitsu-Githubpart
06:12:15  * travis-cijoined
06:12:15  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#116 (master - 28a3b0a : indexzero): The build passed.
06:12:15  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/ecb547223f3f...28a3b0a6f041
06:12:15  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361327
06:12:15  * travis-cipart
06:13:44  * travis-cijoined
06:13:44  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#117 (master - af9eb06 : Charlie Robbins): The build passed.
06:13:44  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/28a3b0a6f041...af9eb06e4779
06:13:44  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361335
06:13:44  * travis-cipart
06:14:42  * Samuel_Roldanquit (Quit: Samuel_Roldan)
06:20:46  * faceleg|sleepjoined
06:27:04  * Nodejitsu-Githubjoined
06:27:04  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/cA1v6g
06:27:04  <Nodejitsu-Github>node-http-proxy/master ef66833 jpetazzo: Fix truncated chunked responses
06:27:04  <Nodejitsu-Github>node-http-proxy/master ba65a48 jpetazzo: Fix typo which slipped in during patch clean-up
06:27:04  * Nodejitsu-Githubpart
06:28:57  * travis-cijoined
06:28:57  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#118 (master - ba65a48 : jpetazzo): The build passed.
06:28:57  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/af9eb06e4779...ba65a485fcf7
06:28:57  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361418
06:28:57  * travis-cipart
06:31:07  * standoojoined
06:47:08  * sreeixjoined
06:49:07  * Nodejitsu-Githubjoined
06:49:07  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 5 new commits to master: http://git.io/fLfoww
06:49:07  <Nodejitsu-Github>node-http-proxy/master 440013c indexzero: [fix doc] Fix bad variable reference in `README.md`.
06:49:07  <Nodejitsu-Github>node-http-proxy/master 9cecd97 indexzero: [minor] s/function(/function (/ s/){/) {/
06:49:07  <Nodejitsu-Github>node-http-proxy/master 4c130f5 Colin Mollenhour: Allow event observers to access upstream response headers and data.
06:49:07  * Nodejitsu-Githubpart
06:49:46  * thepumpkinjoined
06:50:24  * Domenic_quit (Ping timeout: 245 seconds)
06:50:33  * defunctzombie_zzchanged nick to defunctzombie
06:52:04  * travis-cijoined
06:52:04  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#119 (master - b1c4bd6 : colinmollenhour): The build passed.
06:52:04  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/ba65a485fcf7...b1c4bd61e8ae
06:52:04  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361598
06:52:04  * travis-cipart
07:06:03  <maasan>fusiongrokker: Aliases created at https://github.com/fizerkhan/bash-it/blob/master/aliases/available/jitsu.aliases.bash
07:06:32  * kperchjoined
07:08:07  * defunctzombiechanged nick to defunctzombie_zz
07:11:52  * R_Macy_quit (Quit: Computer has gone to sleep.)
07:15:51  * generalissimoquit (Remote host closed the connection)
07:16:05  * nodojoined
07:18:12  <nodo>how can i view a directory on a drone?
07:19:34  <nathan7>nodo: You could add something to your app for it
07:19:55  <nathan7>nodo: Drones are erased on every deploy, you're not expected to keep data on drones
07:20:02  <nathan7>a drone is a fairly throw-away thing
07:20:46  <maasan>nathan7: As nodo asked, we also written our log files under server/var/log/products.log. How can we get this file from drones?
07:21:15  * tonistjoined
07:21:41  <maasan>If deleted in every deploy, where can we write our logs?
07:21:42  <nathan7>maasan: You can just log to stdout
07:21:52  <nathan7>maasan: And use jitsu logs
07:21:53  * Nodejitsu-Githubjoined
07:21:53  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/v3iuPA
07:21:53  <Nodejitsu-Github>node-http-proxy/master 4c1a2c1 indexzero: [fix] Make options immutable in `RoutingProxy`. Fixes #248.
07:21:53  * Nodejitsu-Githubpart
07:22:49  <maasan>We have log into different log files for different metrics analysis. I dont think it is possible with stdout. We need it in different file
07:23:02  * fusiongrokkerquit (Read error: Connection reset by peer)
07:23:08  * fusiongrokker_joined
07:23:34  * sreeixquit (Ping timeout: 256 seconds)
07:23:43  * travis-cijoined
07:23:43  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#120 (master - 4c1a2c1 : indexzero): The build passed.
07:23:43  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/b1c4bd61e8ae...4c1a2c141630
07:23:43  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361846
07:23:43  * travis-cipart
07:24:52  <nathan7>maasan: Then the recommended option is to use a logging-as-a-service service
07:24:58  <nathan7>maasan: like Loggly or something
07:25:15  <nathan7>(though we've had issues with Loggly, but it's the first that popped into my mind)
07:25:53  <maasan>nathan7: okay, understood.
07:26:13  <maasan>We used loggly for logging service
07:26:22  <maasan>whtat is the issue? is still exists?
07:26:33  <nathan7>Yeah, but they've gone down in the past
07:26:46  <nathan7>and had various intermittent issues
07:26:52  <nathan7>Which is annoying because they power jitsu logs
07:28:33  <maasan>now i can use loggly right?
07:28:53  <nathan7>It's what we use, yeah
07:29:34  * sreeixjoined
07:29:53  <maasan>nathan7 thanks
07:29:58  <nathan7>[=
07:30:25  * Nodejitsu-Githubjoined
07:30:25  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/2CFhTA
07:30:25  <Nodejitsu-Github>node-http-proxy/master 3130665 indexzero: [fix] Emit `notFound` event when ProxyTable location does not exist. Fixes #355. Fixes #333.
07:30:25  * Nodejitsu-Githubpart
07:32:12  * travis-cijoined
07:32:12  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#121 (master - 3130665 : indexzero): The build passed.
07:32:12  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/4c1a2c141630...3130665d9f1e
07:32:12  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361886
07:32:12  * travis-cipart
07:35:15  * maasanquit (Quit: Page closed)
07:36:11  * Nodejitsu-Githubjoined
07:36:11  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/Y2je1A
07:36:11  <Nodejitsu-Github>node-http-proxy/master 6a278b3 indexzero: [fix] http-proxy should not modify the protocol in redirect request for external sites. Fixes #359.
07:36:11  * Nodejitsu-Githubpart
07:38:03  * travis-cijoined
07:38:03  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#122 (master - 6a278b3 : indexzero): The build passed.
07:38:03  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/3130665d9f1e...6a278b3dd88d
07:38:03  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361911
07:38:03  * travis-cipart
07:40:33  * Nodejitsu-Githubjoined
07:40:33  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/8gniKQ
07:40:33  <Nodejitsu-Github>node-http-proxy/master a89e2f2 indexzero: [fix] Do not use "Transfer-Encoding: chunked" header for proxied DELETE requests with no "Content-Length" header. Fixes #373.
07:40:33  * Nodejitsu-Githubpart
07:42:17  * travis-cijoined
07:42:18  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#123 (master - a89e2f2 : indexzero): The build passed.
07:42:18  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/6a278b3dd88d...a89e2f2688ff
07:42:18  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361950
07:42:18  * travis-cipart
07:42:25  * kperchquit (Remote host closed the connection)
07:45:08  * Nodejitsu-Githubjoined
07:45:08  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/hT1-Zw
07:45:08  <Nodejitsu-Github>node-http-proxy/master 9be0af3 indexzero: [fix] Set "content-length" header to "0" if it is not already set on DELETE requests. Fixes #338.
07:45:08  <Nodejitsu-Github>node-http-proxy/master 476cbe7 indexzero: [minor] Move private helper to end of file.
07:45:08  * Nodejitsu-Githubpart
07:47:01  * travis-cijoined
07:47:01  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#124 (master - 476cbe7 : indexzero): The build passed.
07:47:01  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/a89e2f2688ff...476cbe741fc4
07:47:01  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5361973
07:47:01  * travis-cipart
07:53:37  * sreeixquit (Ping timeout: 240 seconds)
07:55:53  * SunnyShahjoined
07:56:31  <SunnyShah>Hi nodejitsu support
07:57:14  * sreeixjoined
08:02:48  * distilledchaosquit (Quit: Leaving)
08:03:24  <yawnt>hey SunnyShah :D
08:04:30  * joshonthewebquit (Quit: Computer has gone to sleep.)
08:04:50  * Nodejitsu-Githubjoined
08:04:50  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/pd4lfQ
08:04:50  <Nodejitsu-Github>node-http-proxy/master 89d43c2 pdoran: Added timeout option and test to test new timeout parameter, added requestFail assertion.
08:04:50  * Nodejitsu-Githubpart
08:06:29  * travis-cijoined
08:06:30  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#125 (master - 89d43c2 : pdoran): The build passed.
08:06:30  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/476cbe741fc4...89d43c20dd0d
08:06:30  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5362118
08:06:30  * travis-cipart
08:06:32  * Nodejitsu-Githubjoined
08:06:32  <Nodejitsu-Github>[node-http-proxy] indexzero deleted responsecodes at 3a3336c: http://git.io/-CV1ng
08:06:32  * Nodejitsu-Githubpart
08:07:45  <SunnyShah>yawnt, Hi, Thanks for so quick response!
08:08:01  <yawnt>SunnyShah: what's up? :)
08:08:10  * joshonthewebjoined
08:08:15  <SunnyShah>yawnt, We are considering nodejitsu for our major product.
08:08:40  <yawnt>wonderful! may i ask what is it?
08:10:22  <SunnyShah>It is water distribution monitoring system, We put monitoring devices on hundreds of pumping stations, which sends our app current water pumped, tank level etc. We then show it off live, provide alerts, reports.
08:10:34  <yawnt>wow that's awesome :O
08:10:52  <yawnt>where i live there has been a research team developing something like that for 3rd world countries in africa
08:11:16  <SunnyShah>We are also developing this for India
08:11:24  <SunnyShah>:
08:11:26  <yawnt>except it's like.. more oriented towards managing the routes of water distribution and such
08:11:27  <SunnyShah>:)
08:11:31  <yawnt>sweet!
08:12:10  <SunnyShah>Our requirements are this, We need the servers to be up almost all then time, 5-10 minutes of downtime for a day is the max our system can tolarate.
08:12:31  * fusiongrokker_quit (Quit: fusiongrokker_)
08:12:59  <yawnt>SunnyShah: i see, in this case do you mind writing your case / requirements in an email
08:13:04  <yawnt>and send it to [email protected] ?
08:13:12  <yawnt>so we can follow with you directly 1on1 :)
08:13:28  * Nodejitsu-Githubjoined
08:13:28  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/lkUX5g
08:13:28  <Nodejitsu-Github>node-http-proxy/master 2c36507 Niall O'Higgins: problem: don't want to run my server as root to bind to privileged ports (e.g. 80, 443)....
08:13:28  <Nodejitsu-Github>node-http-proxy/master 10f6b05 Niall O'Higgins: add support for loading CA bundles...
08:13:28  * Nodejitsu-Githubpart
08:13:51  <SunnyShah>Ok, IRC seems very quick, Can we please continue for 2 minutes ( humble request :) ) ?
08:14:13  <SunnyShah>I will surely send the mail.
08:14:30  <yawnt>SunnyShah: please do, i'll be happy to answer at my best any questions you have
08:14:58  <SunnyShah>1). What uptime do you gurantee?
08:15:03  * travis-cijoined
08:15:03  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#126 (master - 10f6b05 : Niall O'Higgins): The build passed.
08:15:03  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/89d43c20dd0d...10f6b0577518
08:15:03  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5362189
08:15:03  * travis-cipart
08:16:31  <SunnyShah>2). How many apps is nodejitsu hosting currently? 3). Who are the major customers?
08:16:49  <yawnt>about the uptime, business plans should be suited for what you're looking for.. to be honest i don't have an exact percentage yet because we launched just a couple weeks ago
08:16:58  <yawnt>(we launched biz plans)
08:17:07  <SunnyShah>Oh! ok
08:17:17  <yawnt>we're hosting apps in order of thousands
08:17:57  * jcrugzzquit (Ping timeout: 248 seconds)
08:18:13  <yawnt>and about the major customers you can have a look at the "Trusted by" section at https://www.nodejitsu.com/
08:18:17  <yawnt>bottom of the page :)
08:18:37  <SunnyShah>yawnt, They are partners right?
08:18:40  * Nodejitsu-Githubjoined
08:18:40  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 3 new commits to master: http://git.io/VAx5TQ
08:18:40  <Nodejitsu-Github>node-http-proxy/master 46b078a Mikkel Garcia: pathnameOnly flag added. Ignores hostname and applies routing table to the paths being requested.
08:18:40  <Nodejitsu-Github>node-http-proxy/master a1607c1 Mikkel Garcia: pathnameOnly option documented in the Readme.md
08:18:40  <Nodejitsu-Github>node-http-proxy/master 5e6be6c Mikkel Garcia: [doc] added comments to pathnameOnly block.
08:18:40  * Nodejitsu-Githubpart
08:18:58  <SunnyShah>Something similar to http://success.heroku.com/ ?
08:19:45  <yawnt>ah, sorry i had misunderstood you.. we don't have a page like that yet, but it's work in progress
08:20:14  <yawnt>SunnyShah: may i ask you an email address just for reference :) ?
08:20:22  <SunnyShah>[email protected]
08:20:26  <yawnt>thanks!
08:20:36  * travis-cijoined
08:20:36  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#127 (master - 5e6be6c : Mikkel Garcia): The build passed.
08:20:36  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/10f6b0577518...5e6be6ccf5a3
08:20:36  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5362210
08:20:36  * travis-cipart
08:25:33  <yawnt>SunnyShah: do you have any other questions? :)
08:25:47  <SunnyShah>yawnt, By any chance, can you please provide list of your noteworthy customers? It can help me a lot to convince my management.
08:27:04  * sreeixquit (Quit: sreeix)
08:27:05  <yawnt>SunnyShah: you should ask for that in the email i told you about :D
08:27:56  <SunnyShah>Ok. Sure. Thanks a lot for your help. It is rare to see good engineers helping customers out. Nodejitsu support seems awsome!
08:28:45  <yawnt>SunnyShah: you're welcome! and thanks :) .. if you happen to bump into problems, feel free to join here (or join anyway for a chat haha :D)
08:29:02  <yawnt>looking forward to seeing your product
08:29:12  <SunnyShah>yawnt, Sure, Thanks
08:33:55  * sreeixjoined
08:35:03  * sreeixquit (Client Quit)
08:40:48  * mmalecki[zzz]changed nick to mmalecki
08:48:36  <SunnyShah>yawnt, Mail sent.
08:49:09  <yawnt>wonderful!
08:51:03  <yawnt>SunnyShah: Ana lives in new york so it's pretty early there, i apologize if you'll have to wait a few hours
08:52:58  * kperchjoined
08:57:50  * kperchquit (Ping timeout: 260 seconds)
09:07:39  * `3rdEdenjoined
09:10:47  * switzjoined
09:12:49  * sreeixjoined
09:17:43  * YoYjoined
09:20:27  * pedrodiasquit (Quit: pedrodias)
09:20:29  * Nodejitsu-Githubjoined
09:20:29  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/TdX3Ow
09:20:29  <Nodejitsu-Github>node-http-proxy/master 5d515e4 indexzero: [api test] Manually merge #195 from @tglines since that fork was deleted. Update tests to use new macros. Fixes #195. Fixes #60.
09:20:29  * Nodejitsu-Githubpart
09:22:28  * travis-cijoined
09:22:29  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#128 (master - 5d515e4 : indexzero): The build passed.
09:22:29  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/5e6be6ccf5a3...5d515e472814
09:22:29  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5362731
09:22:29  * travis-cipart
09:25:45  * sreeixquit (Quit: sreeix)
09:42:21  * nouitfvfjoined
09:42:29  * Nodejitsu-Githubjoined
09:42:29  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 1 new commit to master: http://git.io/y0p_6Q
09:42:29  <Nodejitsu-Github>node-http-proxy/master ea0587a indexzero: [minor] Small whitespace compliance.
09:42:29  * Nodejitsu-Githubpart
09:43:54  * `3rdEdenquit (Remote host closed the connection)
09:44:15  * travis-cijoined
09:44:15  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#129 (master - ea0587a : indexzero): The build passed.
09:44:15  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/5d515e472814...ea0587a8f98b
09:44:15  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5362961
09:44:15  * travis-cipart
10:00:13  * Nodejitsu-Githubjoined
10:00:13  <Nodejitsu-Github>[node-http-proxy] indexzero tagged v0.9.0 at d6b12f9: http://git.io/GeB_WQ
10:00:13  * Nodejitsu-Githubpart
10:02:12  * travis-cijoined
10:02:12  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#130 (master - c68e038 : indexzero): The build passed.
10:02:12  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/ea0587a8f98b...c68e0389120d
10:02:12  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5363100
10:02:12  * travis-cipart
10:09:40  * Nodejitsu-Githubjoined
10:09:41  <Nodejitsu-Github>[node-http-proxy] indexzero tagged v0.9.1 at 7bcae2c: http://git.io/U2gtvQ
10:09:41  * Nodejitsu-Githubpart
10:11:13  * travis-cijoined
10:11:13  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#131 (master - 701dc69 : indexzero): The build passed.
10:11:13  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/c68e0389120d...701dc698e3eb
10:11:13  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/5363160
10:11:13  * travis-cipart
10:21:33  * araljoined
10:22:46  <aral>G’morning, folks. Any word on whether the problems from yesterday have been solved? Would like to know if I can start publicising my little demo :)
10:23:48  <indexzero>aral: They are still a WIP on being completely resolved. Just released a new version of node-http-proxy and working on upstream changes :: https://twitter.com/indexzero/status/310329388027760640
10:23:54  * devdazedquit (Ping timeout: 252 seconds)
10:24:06  * thealphanerdjoined
10:24:10  <indexzero>the underlying issue is non-deterministic in nature, usually `jitsu restart` fixes it, but not always
10:24:33  <aral>Thanks for the update @indexzero — what’s the best place to keep an eye on for an update once it’s been resolved?
10:24:44  <indexzero>we're going to publish a complete post-mortem on Monday
10:24:55  <indexzero>so check the blog
10:25:04  <aral>Perfect, thank you :) Hope you guys get to enjoy at least a bit of your weekend. Good luck with all this.
10:25:26  <indexzero>aral: Yeah, me too
10:25:28  <indexzero>ttyl
10:25:34  <aral>l8r :)
10:25:46  * eschnoujoined
10:26:45  * devdazedjoined
10:33:41  * aralquit (Remote host closed the connection)
10:40:37  * `3rdEdenjoined
10:41:05  * eschnouquit (Ping timeout: 260 seconds)
10:44:32  * eschnoujoined
10:55:05  * eschnouquit (Ping timeout: 260 seconds)
10:55:14  * tonistquit (Quit: tonist)
10:59:30  * sreeixjoined
11:06:49  * YoYquit (Quit: Leaving...)
11:09:18  * Domenic_joined
11:10:37  * thl0joined
11:14:25  * YoYjoined
11:14:59  * thl0quit (Ping timeout: 245 seconds)
11:26:44  * rickibalboajoined
11:28:38  * Domenic_quit (Ping timeout: 250 seconds)
11:28:45  * thealphanerdquit (Quit: thealphanerd)
11:38:25  * `3rdEdenquit (Remote host closed the connection)
11:47:18  * sreeixquit (Quit: sreeix)
11:54:03  * indexzeroquit (Quit: indexzero)
12:19:49  * wiherek__joined
12:27:04  * davidbanhamjoined
12:32:26  * `3rdEdenjoined
12:43:50  * jetiennequit (Quit: jetienne)
12:45:59  * davidbanhamquit (Remote host closed the connection)
12:47:17  * standooquit (Quit: Leaving.)
12:48:55  * hallasjoined
13:02:39  * blakmatrixjoined
13:04:07  * faceleg|sleepquit (Ping timeout: 240 seconds)
13:08:29  * blakmatrixtopic: Nodejitsu - Cloud Status https://status.jit.su | Versions: The Node.js Content Delivery Network https://t.co/Rc4YeHfHwk
13:12:03  * fusiongrokkerjoined
13:15:15  * tonistjoined
13:16:01  * marcello3djoined
13:30:37  * jahajoined
13:31:07  * jahaquit (Client Quit)
13:31:40  * jahajoined
13:47:42  * cianomaidinjoined
13:50:11  * therealkoopaquit (Remote host closed the connection)
13:51:32  * drewwwjoined
13:54:15  * lpinjoined
14:02:25  <blakmatrix>Hows everybody doing this morning?
14:04:51  <dscape>hey blakmatrix
14:05:00  <dscape>mornin
14:05:05  <blakmatrix>dscape: morning
14:12:47  <zarac>g'mornin' ; )
14:12:57  <zarac>confused as usual. : )
14:14:00  <blakmatrix>zarac: some coffee might fix that ;)
14:17:23  <lpin>hey blakmatrix, not bad just a little headache
14:17:59  <blakmatrix>lpin: coffee/water can fix that sometimes... or for me a good long shower :D
14:18:14  <lpin>i probably slept too much
14:18:16  <lpin>;)
14:18:32  <blakmatrix>ah I hate those
14:19:31  <blakmatrix>lpin: in that case some calisthenics are in order ;) get the bod moving and the blood pumping
14:20:00  <lpin>gonna take a run later
14:20:31  <lpin>weather is good so no reason for not going
14:20:49  <lpin>spring is in the air \o/
14:21:11  <zarac>blakmatrix: It's "evening" for me now so i should head to the sack. Also, I've already drunk enough coffee today. ; &
14:21:19  <zarac>Water on the other hand.. ; )
14:22:11  <blakmatrix>zarac: or maybe booze ;)
14:22:20  <zarac>haha : )
14:22:27  <zarac>I'm gonna grab a beer, hi5.
14:22:30  <zarac>; )
14:24:53  <blakmatrix>can't wait til St.Patty's day gonna get some guiness (or perhaps some other dark imperial russion stout) make my yearly brisket and onion soup
14:26:12  <zarac>sounds yummy : 0
14:26:14  <blakmatrix>the onion soup uses beer and beef broth, then at the end you have some soda bread slices you put on top, with slices of irish cheese, put that in the oven for a bit
14:26:18  <zarac>cheers, btw =D
14:26:27  <zarac>mmMmMmm.. tasty
14:26:33  <blakmatrix>yes very
14:26:46  <blakmatrix>only downside is you smell like an onion for the next 2 days LOL
14:27:21  <zarac>Hehe.. i don't know anything about that. Something i've never experienced. Maybe 'cause i like onions so much. :0
14:29:42  <blakmatrix>zarac: oh no you'll notice... Youl wake up the next morning to take a shower... and bam, you'll smell the onions ;)
14:29:52  <lpin>ahah
14:30:06  <blakmatrix>if you dont use too much deoderant... onions :P
14:30:15  <blakmatrix>and I hear my breath smells like it too :P
14:30:29  <lpin>perfect before a date i guess
14:30:51  * sreeixjoined
14:31:02  <blakmatrix>lol
14:31:03  * Samuel_Roldanjoined
14:31:26  <lpin>:>
14:32:19  <zarac>I've never smelled onions.. not even garlic. I'm not quite sure what people are talking about. ;7
14:32:50  <zarac>I don't personally know what garlic breath is. :(
14:33:23  <blakmatrix>lol really?
14:33:48  <blakmatrix>such distinct smells
14:34:30  <zarac>I know..
14:34:33  <zarac>well.. i don't know.. rather ; )
14:34:43  <lpin>i know what blakmatrix is talking about, we have a popular event close to where i live "onions festival"
14:34:46  <zarac>People have called me strange before...
14:34:50  <lpin>i let you imagine the rest
14:34:53  <zarac>: )
14:35:48  <lpin>anyway the meals are delicious
14:35:55  <zarac>I bet. ; )
14:36:54  * jetiennejoined
14:37:17  <lpin>but for the next 2 day even you own sweat smell like onions
14:37:18  <lpin>lol
14:46:11  * jlankquit (Remote host closed the connection)
14:46:45  * jlankjoined
14:50:07  * sreeixquit (Ping timeout: 240 seconds)
15:11:09  * jlankquit (Remote host closed the connection)
15:18:19  * `3rdEdenquit (Remote host closed the connection)
15:32:37  * juliangruber1joined
15:36:02  * _7eicherjoined
15:39:31  * marcello3dquit (Remote host closed the connection)
15:41:34  * jlankjoined
15:44:37  <_7eicher>Hi, is it possible to use node-spdy with nodejitsu?
15:48:53  * `3rdEdenjoined
15:49:36  * jlankquit (Ping timeout: 245 seconds)
15:53:07  * cianomaidinquit (Quit: cianomaidin)
15:53:35  <booyaa|foo>dudes if my app generates text files is there an easy way to grab these off the drone?
15:54:41  <booyaa|foo>only way i can think of is write code that s/ftp's off to another server or place in a http gettable bit of the drone
15:55:32  <nathan7>booyaa|foo: err
15:55:35  <nathan7>booyaa|foo: Logfiles?
15:56:44  <booyaa|foo>nah just temporary files i.e. twitter.rss > tranposetext.txt > blah.csv
15:56:57  <booyaa|foo>the temp files nmight be used to troubleshoot if the app fails
15:57:15  * `3rdEdenquit (Ping timeout: 260 seconds)
15:57:28  <booyaa|foo>not worried if someone comes across them, but being able to get them off the drone would be nice.
15:57:32  <nathan7>booyaa|foo: I know a few people use the Dropbox API
15:57:53  <booyaa|foo>yeah i might do that, already using dropbox for other stuff
15:59:10  <booyaa|foo>cheers bud
15:59:30  <booyaa|foo>heh kinda stoked this is my first serious project :D
15:59:45  <nathan7>..aaaand Club Mate and vodka are an awful combination
15:59:48  <booyaa|foo>got some interest from the little printer guys
15:59:51  <booyaa|foo>nathan7: yeah i prefer rum
16:00:00  <booyaa|foo>do you lke club mate as a taste?
16:00:03  <nathan7>yes
16:00:09  <nathan7>we mixed a bunch with rum a while ago
16:00:18  <nathan7>That was the most awful drink I ever had.
16:00:21  <booyaa|foo>tschunk's a nice cm drink
16:00:21  <booyaa|foo>hahaha
16:01:28  <booyaa|foo>pondering what to use for analytics, tempted to just cheat and stick google analytics in for now.
16:01:38  <mmalecki>did someone say 'vodka'
16:01:42  <mmalecki>booyaa|foo: GODOT
16:01:51  <mmalecki>I think someone said vodka
16:02:37  <booyaa|foo>you got a url? getting too many waiting for godot hits :P
16:03:20  <_7eicher>does anyone tried google spdy protocol over nodejitsu cloud?
16:04:26  <nathan7>mmalecki: yes
16:04:32  * cianomaidinjoined
16:04:49  <nathan7>_7eicher: I'm not sure
16:08:24  <booyaa|foo>_7eicher: https://blog.nodejitsu.com/what-is-node-spdy
16:10:38  <mmalecki>_7eicher: currently our balancers terminate spdy
16:10:45  <mmalecki>and you can only use http
16:10:56  <mmalecki>also what do I make for dinner today?
16:13:55  <_7eicher>@mmalecki: do have plans to support ssl or spdy in future, we would realy like to see this!
16:13:58  <nathan7>I am eating peanuts as really late lunch
16:14:10  <nathan7>_7eicher: Our load balancer get SPDY, your app receives HTTP
16:15:13  <mmalecki>_7eicher: we in fact do
16:16:44  * jlankjoined
16:17:18  <_7eicher>@mmalecki: okay, thats great to know... could i test this over the trial plan that you have?
16:18:01  * sreeixjoined
16:18:36  * lresendejoined
16:18:41  <booyaa>mmalecki: steak and chips
16:18:44  * cianomaidinquit (Quit: cianomaidin)
16:18:53  <booyaa>mmalecki: that or a big ass burger with fries
16:21:35  <nathan7>_7eicher: *.jit.su has SSL
16:21:39  <nathan7>_7eicher: (and *.nodejitsu.com)
16:21:54  <nathan7>_7eicher: for business plans, there's SSL on custom domains
16:24:10  * russfrankquit (Ping timeout: 250 seconds)
16:25:33  <_7eicher>+nathan7: as i read SSL is required for spdy, so thats fine... can i see how that practically works over the trial plan?
16:25:43  * jlankquit (Ping timeout: 276 seconds)
16:26:11  * Fishrock123joined
16:27:21  * R_Macy_joined
16:30:30  * defunctzombie_zzchanged nick to defunctzombie
16:31:48  * jcrugzzjoined
16:34:47  <jesusabdullah>jesus http-proxy issues got hammered today
16:35:03  <jesusabdullah>yes I still follow http-proxy what of it
16:36:13  <mmalecki>jesusabdullah: they did :)
16:36:34  * tonistquit (Quit: tonist)
16:36:40  * juliangruber1quit (Remote host closed the connection)
16:38:48  * _7eicherquit (Ping timeout: 245 seconds)
16:41:15  * defunctzombiechanged nick to defunctzombie_zz
16:42:22  * sreeixquit (Quit: sreeix)
16:42:48  * generalissimojoined
16:43:40  <jcrugzz>[0] powered through issues last night
16:48:41  * russfrankjoined
16:51:52  * jlankjoined
16:54:42  * defunctzombie_zzchanged nick to defunctzombie
17:00:49  * jlankquit (Ping timeout: 276 seconds)
17:02:06  * rickibalboaquit (Ping timeout: 245 seconds)
17:06:18  * Fishrock123quit (Remote host closed the connection)
17:20:32  * evan__joined
17:20:47  <evan__>is it down right now? I can't connect to my app
17:22:30  * rickibalboajoined
17:23:15  <jcrugzz>evan__: what error are you getting?
17:23:29  <evan__>no error, it just seems to hang
17:23:40  <evan__>while browser is loading
17:23:54  <evan__>tried starting and re-starting the app, didn't work
17:24:15  <evan__>can you try going to http://nbawowy.com
17:26:40  * Fishrock123joined
17:26:58  * jlankjoined
17:28:05  <jcrugzz>sure
17:29:13  <evan__>it's strange, the admin page says the app has started, it works when I run it on localhost, but it's not loading from nodejitsu
17:29:36  <jcrugzz>evan__: can you gist me your package.json?
17:29:59  <evan__>{ "name": "shotdb", "scripts": { "start": "app.js" }, "version": "0.3.0-104", "engines": { "node": "0.8.x" }, "subdomain": "ezamir.mongotest", "domains": [ "nbawowy.com" ], "dependencies": { "express": "3.x", "mongodb": "*", "jade": "*" } }
17:31:33  * anoemijoined
17:32:00  <nathan7>evan__: hmm, weird
17:32:07  <jcrugzz>evan__: can you change your subdomain to ezamir-mongotest and redeploy?
17:32:09  <nathan7>evan__: from the drone itself I get cannot get /
17:32:10  <evan__>hey, it just loaded...
17:32:14  <evan__>did somebody do something?
17:32:20  <evan__>seems to be working now
17:32:59  <evan__>i'll take it, but kind of a mystery to me why it didn't load
17:34:56  * anoemiquit (Client Quit)
17:35:01  * jlankquit (Ping timeout: 245 seconds)
17:35:43  * Fishrock123quit (Remote host closed the connection)
17:36:33  <nathan7>evan__: err
17:36:43  <nathan7>evan__: Your domain resolves to 192.31.186.142
17:37:20  <jcrugzz>evan__: it doesn't seem like your nbawowy.com domain is linked to your app
17:40:17  * YoYquit (Ping timeout: 256 seconds)
17:42:54  <evan__>So the problem might be a domain forwarding issue?
17:42:56  * YoYjoined
17:44:30  * acejoined
17:45:07  <ace>hello, is it possible to see the log output in the cmd window where I do the deploys?
17:45:21  <ace>or is it just through the cp on the site?
17:45:44  <jcrugzz>evan__: yea make sure you set your A records for your domain following instructions here http://dns.jit.su/
17:46:05  <jcrugzz>just run a `host nodejitsu.com` to get the updated IPs
17:46:19  <jcrugzz>ace: you can run `jitsu logs` in the directory of the app
17:46:29  <ace>cool
17:46:34  <evan__>thanks
17:46:35  <evan__>quit
17:46:43  * evan__quit (Quit: Page closed)
17:46:46  * sirkitreechanged nick to sirkitree|afk
17:46:55  <ace>oh and I can't seem to get the domain working when it's without the 'www'
17:47:05  <ace>I followed the instructions and added all the A records.
17:47:14  <ace>and JSON package has both listed
17:48:27  <jcrugzz>ace: can you gist me your package.json?
17:48:57  <ace>sure
17:50:08  <ace>https://gist.github.com/anonymous/1d075eed376b723abc7a
17:51:31  <jcrugzz>ace: ok so you need to setup a CNAME for the www extension on your DNS
17:51:39  <jcrugzz>you probably have it setup for the host
17:53:14  <jcrugzz>ace: make a cname for the www in your host records and point it at your @
17:54:43  <ace>what's the @?
17:55:02  <jcrugzz>the @ is your worldwarpong.com address in your host records usually
17:55:28  <jcrugzz>that should have an A record for all the load balancers listed when you run a `host nodejitsu.com`
17:55:51  <Samuel_Roldan>why the server takes SO long to respond from time to time? is it rebuilding some cache or something?
17:56:23  <jcrugzz>Samuel_Roldan: can you gist me your package.json?
17:56:27  <Samuel_Roldan>def
17:56:53  <Samuel_Roldan>https://gist.github.com/sam3k/5f3a65aa0ee5e1695ebc
17:57:18  <ace>so far there is just a load of * A entries pointing to the various IPs. No @ entry. Is this a CNAME to worldwarpong.com.?
17:57:59  <Samuel_Roldan>that is correct. i did not set any @ entries per customer support from my domain provider
17:58:09  <Samuel_Roldan>oh
17:58:14  <Samuel_Roldan>my bad. nm
18:00:17  <Samuel_Roldan>jcrugzz any ideas?
18:01:00  <jcrugzz>ace: i guess it depends on your dns provider. and @ would be equivalent to worldwarpong.com.
18:01:07  <jcrugzz>Samuel_Roldan: one second :)
18:01:13  <Samuel_Roldan>np :)
18:01:20  <jcrugzz>ace: ill show you what mine look like as an example
18:01:35  <ace>cool thanks
18:02:05  * jlankjoined
18:05:12  * SunnyShahquit (Quit: Leaving)
18:05:33  * ramitosjoined
18:05:38  <jcrugzz>ace: https://dl.dropbox.com/u/14043606/Screen%20Shot%202013-03-09%20at%201.04.47%20PM.png
18:05:51  <jcrugzz>Samuel_Roldan: checking out yours now
18:05:53  * caseywebdevjoined
18:06:04  <Samuel_Roldan>Thanks jcrugzz
18:07:04  <caseywebdev>is it possible to get pg.native running on nodejitsu or is it just the pure-js implementation that will run?
18:07:44  * faceleg|sleepjoined
18:08:00  <ace>thanks jcrugzz, mine is looking like that now so hopefully it will work when kicks in
18:08:44  <jcrugzz>caseywebdev: you mean something like this? https://npmjs.org/package/pg
18:08:54  <jcrugzz>ace: np and yea let me know
18:09:16  <jcrugzz>Samuel_Roldan: your app loads fine, any delay is caused by how you are serving static assets
18:09:50  <jcrugzz>i would either use a CDN like s3 or build your own CDN with https://npmjs.org/package/versions if you are adventurous :)
18:10:05  <Samuel_Roldan>what do you mean by "how i load "
18:10:11  * c4milojoined
18:10:26  * jlankquit (Ping timeout: 245 seconds)
18:11:11  <Samuel_Roldan>I'm using express.static to load static files
18:11:13  <jcrugzz>Samuel_Roldan: im not particularly sure how require.js works but does it not have a certain build script of sorts?
18:11:22  * caseywebdevquit (Remote host closed the connection)
18:11:25  <Samuel_Roldan>it does
18:11:48  <Samuel_Roldan>i minified most of the js and css
18:13:16  <Samuel_Roldan>I'm doing another deploy right now with logs everywhere to see if i can find any app bottlenecks
18:13:53  <jcrugzz>Samuel_Roldan: ok, well loading static assets in that fashion won't be as fast as if its being loaded via CDN.
18:13:57  <jcrugzz>but slick little site
18:14:10  <Samuel_Roldan>Thank you jcrugzz :)
18:14:54  <Samuel_Roldan>right, i totally understand that nothing beats a CDN, but it shouldn't be THAT slow from time to time. It's like it happens once every 15m or 30mins then it loads super fast
18:15:00  * faceleg|sleepquit (Quit: WeeChat 0.3.9.2)
18:15:39  * caseywebdevjoined
18:16:13  * caseywebdevquit (Remote host closed the connection)
18:17:14  <jcrugzz>Samuel_Roldan: Im not particularly a fan of how connect middleware handles things (it doesn't stream the assets). And it took me 2.15s to load it
18:18:10  <Samuel_Roldan>Got it. Well, I'm going to start paying attention to connect's performance and follow your advice and use CDN sometime in the near future.
18:18:32  <jcrugzz>Samuel_Roldan: cool well best of luck :)
18:18:48  <Samuel_Roldan>Thanks jcrugzz, cheers!
18:21:24  * defunctzombiechanged nick to defunctzombie_zz
18:21:40  <Samuel_Roldan>jcrugzz, once last question. You guys don't support use of varnish within nodejitsu?
18:22:04  <jcrugzz>Samuel_Roldan: everything is 100% node.js. no need for anything like that :)
18:22:17  <Samuel_Roldan>Understood. :D
18:28:13  * caseywebdevjoined
18:28:31  * caseywebdevquit (Remote host closed the connection)
18:28:55  * lpinquit (Ping timeout: 260 seconds)
18:37:13  * jlankjoined
18:44:40  * `3rdEdenjoined
18:45:42  * jlankquit (Ping timeout: 264 seconds)
18:48:00  * jcrugzzquit (Quit: Lost terminal)
18:53:50  * Samuel_Roldanquit (Quit: Samuel_Roldan)
19:00:05  * defunctzombie_zzchanged nick to defunctzombie
19:01:30  * defunctzombiechanged nick to defunctzombie_zz
19:02:25  * jcrugzzjoined
19:02:26  * lresendequit (Quit: Zzzzzzz ...)
19:04:15  * joshonthewebquit (Quit: Computer has gone to sleep.)
19:12:21  * jlankjoined
19:15:50  * c4miloquit (Remote host closed the connection)
19:21:06  * jlankquit (Ping timeout: 264 seconds)
19:21:20  * rickibalboaquit (Read error: Connection reset by peer)
19:21:33  * rickibalboajoined
19:22:03  * DTrejojoined
19:27:48  * rickibalboaquit (Ping timeout: 264 seconds)
19:33:13  * TooTallNatejoined
19:36:48  * generalissimoquit (Remote host closed the connection)
19:47:28  * jlankjoined
19:51:23  * c4milojoined
19:54:00  * Mikeumusjoined
19:55:32  * acequit (Quit: Page closed)
19:55:51  * jlankquit (Ping timeout: 245 seconds)
19:58:33  * lpinjoined
20:04:40  * tonistjoined
20:08:09  * anoemijoined
20:13:39  * joshonthewebjoined
20:22:28  * jlankjoined
20:25:22  * c4miloquit (Remote host closed the connection)
20:28:22  * lresendejoined
20:30:51  * jlankquit (Ping timeout: 245 seconds)
20:33:31  * c4milojoined
20:33:36  * lresendequit (Quit: Zzzzzzz ...)
20:36:43  * bardujoined
20:39:09  * lwicksjoined
20:41:18  * alexpoljoined
20:42:05  <alexpol>Hello, can not deploy new app: after "info: Creating snapshot 0.0.1-1" string_decoder.js:117 var i = (buffer.length >= 3) ? 3 : buffer.length; ^ TypeError: Cannot read property 'length' of null
20:42:26  * Nodejitsu-Githubjoined
20:42:27  <Nodejitsu-Github>[jitsu] blakmatrix deleted arg_currying_congruity_jul_2012 at 896cae4: http://git.io/hFKGtg
20:42:27  * Nodejitsu-Githubpart
20:44:14  <jcrugzz>alexpol: can you run `jitsu deploy --debug` and pm me the gist of the response?
20:50:32  * cianomaidinjoined
20:51:33  * c4miloquit (Remote host closed the connection)
20:51:34  * araljoined
20:54:40  <alexpol>jcrugzz: hm, I have this problem only in WebStorm IDE Command Line tool, so thanks won't be using it --debug there actually gives the same result.
20:55:12  <aral>Hey guys, I’m sure you’ve had a rather hectic weekend — hope things are looking better. My site seems to be reachable now and thank you for getting right on top of it. *virtual hugs*
20:57:34  * jlankjoined
20:57:44  <jcrugzz>alexpol: interesting, not familiar with using that command line tool.
20:58:30  <mmalecki>aral: yup, we deployed 2 fixes yesterday, 2 different services
20:58:45  <mmalecki>aral: I keep monitoring the situation and it's looking waaay better
20:58:54  * Mikeumusquit (Ping timeout: 250 seconds)
21:00:07  <aral>@mmalecki Good work :) Here’s hoping it’ll be a distant memory soon. My girlfriend was able to access it for the first time today and my deploys are succeeding :) Thanks again.
21:00:30  <mmalecki>aral: pleasure. thanks for following me on twitter too :)
21:01:07  <mmalecki>aral: not sure if you've heard, but there'll be a post-mortem published
21:01:27  <mmalecki>aral: once again, sorry for problems over the weekend
21:01:42  <aral>@mmalecki Of course — I’m sure there’s lots I’ll be learning from you :) Only recently started really playing with Node (after dabbling off and on) and *loving* it. And loving Nodejitsu too. So elegant :)
21:02:41  <aral>@mmalecki No worries, man. Shit happens. You guys are creating pioneering stuff—things are bound to go wrong sometimes. It’s probably a good sign that you’re heading in the right direction :)
21:03:01  * TooTallNatequit (Quit: Computer has gone to sleep.)
21:03:05  * jcrugzzquit (Read error: Connection reset by peer)
21:03:05  * jcrugzz_joined
21:03:10  <mmalecki>here's to hoping that it is :). expect more cool stuff soon!
21:05:37  * jlankquit (Ping timeout: 248 seconds)
21:05:40  * jcrugzz_changed nick to jcrugzz
21:08:51  <alexpol>jcrugzz: it is just a tool inside IDE that runs cmd in console, here is the full output: http://chopapp.com/#e7hi5q0b
21:09:34  * cianomaidinquit (Quit: cianomaidin)
21:09:39  <nathan7>alexpol: is it trying to ask you something?
21:09:46  <nathan7>alexpol: as in a prompt
21:12:08  <alexpol>+nathan7: no, just throws the error
21:12:53  <nathan7>alexpol: I mean, if it were to not crash
21:13:01  <nathan7>alexpol: if you run it in an actual console right after
21:13:06  <nathan7>alexpol: does it ask you something?
21:13:18  <nathan7>alexpol: because my guess is that it is crashing while trying to ask you something
21:13:55  <alexpol>hm yes perhaps it should ask about confirmation
21:14:06  <alexpol>It didn't ask
21:15:16  * kperchjoined
21:16:32  <nathan7>because presumably WebStorm is not spawning an actual terminal, just a pipe
21:19:19  * cianomaidinjoined
21:19:29  * kperchquit (Ping timeout: 248 seconds)
21:21:32  * cianomaidinquit (Client Quit)
21:26:44  * generalissimojoined
21:27:24  * cianomaidinjoined
21:27:57  * lwicksquit (Remote host closed the connection)
21:28:46  * `3rdEdenquit (Remote host closed the connection)
21:28:47  * lwicksjoined
21:30:39  * tonistquit (Quit: tonist)
21:30:54  * c4milojoined
21:31:14  * lwicksquit (Client Quit)
21:32:23  * jlankjoined
21:34:15  * cianomaidinquit (Quit: cianomaidin)
21:37:53  * c4miloquit (Remote host closed the connection)
21:40:26  * jlankquit (Ping timeout: 245 seconds)
21:42:17  * lpinquit (Quit: Leaving)
21:47:54  * russfrankquit (Ping timeout: 245 seconds)
21:48:58  * russfrankjoined
21:50:13  * lresendejoined
21:50:59  * Samuel_Roldanjoined
21:52:44  * moneypennyjoined
21:53:05  * moneypennyquit (Client Quit)
21:55:02  * alexpolquit (Ping timeout: 245 seconds)
21:59:15  * anoemiquit (Quit: anoemi)
22:02:48  * lwicksjoined
22:03:14  * aralquit (Remote host closed the connection)
22:03:46  <jetienne>q. is there a way to get the snapshot version from inside the running node ?
22:05:51  <jetienne>silly me i can read package.json :)
22:06:01  * cronopiojoined
22:06:36  * wiherek__quit (Ping timeout: 276 seconds)
22:06:58  * jlankjoined
22:11:58  * cianomaidinjoined
22:16:04  * jlankquit (Ping timeout: 276 seconds)
22:17:55  <nathan7>jetienne: require('./package.json')
22:17:59  <nathan7>jetienne: [=
22:18:56  <jetienne>nathan7: require works with plain json files ? i wasn't aware. cool :)
22:19:27  <nathan7>jetienne: ~ it's a kind of magic ~
22:19:54  <nathan7>jetienne: (or perhaps it's just require.extensions['.json'], whatever explanation pleases you)
22:20:13  * kdetellajoined
22:20:49  * russfrankquit (Ping timeout: 245 seconds)
22:21:02  <kdetella>I keep getting: Nodejitsu Error (500): Internal Server Error
22:21:03  <kdetella>error: socket hang up … anyone have a clue as to whats up?
22:21:25  <kdetella>* on 'jitsu apps deploy'
22:21:58  * nathan7puts a hard-hat on
22:22:26  * Mikeumusjoined
22:22:28  <nathan7>kdetella: is your app very large?
22:23:48  <kdetella>nathan7: not really. i successfully deployed several iterations yesterday. only changes today are css and markup
22:23:55  <nathan7>kdetella: Mhm, can you run that with --debug
22:24:40  <kdetella>Ran w/ --debug
22:24:48  <kdetella>still 500 socket hang-up
22:25:06  <kdetella>anything specific you would need to see to maybe help?
22:26:13  <nathan7>Seems to be on our side
22:26:18  <nathan7>Rocket surgery in progress, please stand by
22:26:31  <kdetella>Awesome. Thanks.
22:27:34  * mmaleckichanged nick to mmalecki[zzz]
22:28:07  * cianomaidinquit (Quit: cianomaidin)
22:28:25  <nathan7>kdetella: What API call is it failing on?
22:28:30  <nathan7>kdetella: (ie what URL)
22:28:56  <nathan7>kdetella: or just gist the whole debug log
22:30:48  * cianomaidinjoined
22:31:29  <kdetella>nathan7: https://gist.github.com/kyledetella/5126054
22:32:31  <nathan7>kdetella: Thank you [=
22:33:07  <kdetella>Yep.
22:33:33  <sberryman>blakmatrix: you around?
22:33:40  <nathan7>kdetella: This happens repeatedly?
22:33:52  <kdetella>yes. several times today
22:33:54  * russfrankjoined
22:34:04  <kdetella>nathan7: each time i have tried today
22:34:07  <nathan7>kdetella: and that's the entire output? (no stack trace?)
22:34:20  * Mikeumusquit (Read error: Connection reset by peer)
22:34:32  <kdetella>nathan7: this is what i left out
22:34:38  <kdetella>error: Error running command apps deploy
22:34:39  <kdetella>error: Nodejitsu Error (500): Internal Server Error
22:34:39  <kdetella>error: socket hang up
22:34:58  <nathan7>kdetella: mhm
22:36:11  <nathan7>kdetella: Could you gist a non-debug log?
22:36:16  <kdetella>yes
22:37:17  <kdetella>nathan7 this is the entire output in my terminal
22:37:19  <kdetella>https://gist.github.com/kyledetella/5126079
22:37:24  <kdetella>w/o --debug
22:41:27  * thepumpkinquit (Ping timeout: 260 seconds)
22:41:29  * jlankjoined
22:41:30  * wiherek__joined
22:41:43  * OliverJAshjoined
22:44:33  * Mikeumusjoined
22:44:42  <nathan7>kdetella: Could you try incrementing the snapshot number?
22:44:55  <kdetella>nathan7 yes
22:44:59  * cianomaidinquit (Ping timeout: 245 seconds)
22:46:33  <nathan7>kdetella: Does that change the deployment result?
22:46:38  <nathan7>??????????//
22:46:41  <kdetella>unfortunately no
22:46:55  <nathan7>sorry about that, crumb under my ? key
22:47:01  <nathan7>kdetella: mhm
22:47:04  <kdetella>haha
22:48:35  <nathan7>kdetella: pack=$(npm pack); du -h $pack; rm -f $pack
22:48:41  <nathan7>kdetella: What does that yield? (run in your app dir)
22:49:16  <kdetella>nathan7 ... well I manually updated the snapshot number and it did not work. Then...just on a whim, I deleted : "env": "development", from my package.json
22:49:21  <kdetella>and that worked
22:49:37  * jlankquit (Ping timeout: 248 seconds)
22:49:51  <nathan7>kdetella: Interesting!
22:50:16  <kdetella>nathan7 should I still run that command you sent?
22:50:19  <nathan7>kdetella: Can you gist your entire package.json? (as it was before)
22:50:25  <kdetella>yes
22:50:30  <nathan7>kdetella: Yeah, that just figures out how large your app is
22:50:40  * pedrodiasjoined
22:50:42  <nathan7>kdetella: as far as I can tell it's 3.9MB but I'm trying to rule everything weird out
22:51:15  * wiherek__quit (Ping timeout: 260 seconds)
22:51:30  <kdetella>nathan7 ok i will run that. here is the package.json BEFORE i removed the "env" : https://gist.github.com/kyledetella/5126138
22:51:52  <nathan7>kdetella: Thank you! Seems this is reproducible
22:52:14  <kdetella>nathan7 ok. interesting. well I guess i should keep that out of my package.json, huh?
22:52:21  <kdetella>also, the output was: 3.9M kyledetella-0.0.1-3.tgz
22:52:24  <nathan7>kdetella: What was it supposed to do?
22:52:58  <kdetella>actually it was in there because I used this file from an older app. it has no purpose, I just missed it
22:53:22  <kdetella>and clearly, that is not how you set environment variables on nodejistu, correct?
22:53:59  <nathan7>kdetella: Ah!
22:54:04  * OliverJAshquit (Quit: OliverJAsh)
22:54:13  <nathan7>kdetella: env is expected to be an object
22:54:29  <nathan7>kdetella: what you probably intended: "env": { "NODE_ENV": "development" }
22:54:48  <nathan7>That explains the mysterious crash
22:54:59  * Mikeumusquit (Ping timeout: 245 seconds)
22:55:06  <kdetella>nathan7, yes, that would work MUCH better. I don't necessarily need that now, but I will use it.
22:55:20  <kdetella>thank you so much for your help and looking into things for me. much appreciated
23:00:42  * OliverJAshjoined
23:06:47  * ferloresjoined
23:07:03  * jcrugzzquit (Ping timeout: 276 seconds)
23:11:06  * Mikeumusjoined
23:14:36  * lwicksquit (Ping timeout: 240 seconds)
23:16:20  * jlankjoined
23:16:40  * jcrugzzjoined
23:17:01  * TooTallNatejoined
23:18:22  * admcjoined
23:18:22  * admcquit (Client Quit)
23:19:26  * admcjoined
23:21:43  * jcrugzzquit (Ping timeout: 276 seconds)
23:24:58  * jlankquit (Ping timeout: 276 seconds)
23:25:17  <sberryman>what are you guys using for ssl? built in https module?
23:28:12  <nathan7>sberryman: Yar, core HTTPS.
23:28:24  <sberryman>figured, thanks
23:28:33  <nathan7>sberryman: see node-http-proxy
23:28:43  <nathan7>sberryman: https://github.com/nodejitsu/node-http-proxy
23:28:47  <sberryman>the core team is working on ssl performance i'm assuming
23:29:16  <nathan7>I believe so, yeah
23:34:51  * defunctzombie_zzchanged nick to defunctzombie
23:35:13  <sberryman>nathan7: thanks, i wonder how the performance compares to stud or pound
23:35:33  <nathan7>sberryman: benchmark benchmark benchmark!
23:35:40  <sberryman>lazy lazy lazy :)
23:35:45  <sberryman>trying to find someone that already has :)
23:35:47  <nathan7>the one thing I learnt about performance is that all your guesses are wrong
23:36:31  * jgablejoined
23:38:20  * wiherek__joined
23:38:37  * ChaoticJorgejoined
23:39:05  * erichocean_joined
23:43:35  * defunctzombiechanged nick to defunctzombie_zz
23:44:13  * standoojoined
23:44:17  * thepumpkinjoined
23:47:27  * hallasquit (Quit: ["Textual IRC Client: www.textualapp.com"])
23:47:35  * jgablequit (Quit: Textual IRC Client: www.textualapp.com)
23:51:14  * jlankjoined
23:55:24  * cianomaidinjoined
23:56:41  * wiherek__quit (Ping timeout: 245 seconds)