00:01:22  * mdedetrichjoined
00:02:53  * benv_quit (Quit: Computer has gone to sleep.)
00:03:46  * benv_joined
00:06:11  * DTrejoquit (Remote host closed the connection)
00:06:53  * mdedetrichquit (Quit: Computer has gone to sleep.)
00:07:32  * coderarityjoined
00:07:56  * towskijoined
00:11:57  * mdedetrichjoined
00:12:53  * benv_quit (Quit: Computer has gone to sleep.)
00:13:45  * thl0quit (Remote host closed the connection)
00:27:28  * joshonthewebquit (Quit: Computer has gone to sleep.)
00:31:47  * _sorensenquit (Quit: _sorensen)
00:35:59  * _sorensenjoined
00:39:58  * ravivmgjoined
00:42:54  * ravivmgquit (Client Quit)
00:43:36  * ravivmgjoined
00:49:34  * ravivmgpart
00:49:51  * ravivmgjoined
00:51:18  * davidbanhamjoined
00:51:38  * anoemiquit (Quit: anoemi)
00:55:52  * cjmquit (Remote host closed the connection)
00:56:16  * davidbanhamquit (Remote host closed the connection)
00:56:35  * davidbanhamjoined
00:59:15  * towskiquit (Remote host closed the connection)
00:59:55  * benv_joined
01:01:08  * Slyjoined
01:04:05  * cjmjoined
01:07:00  * towskijoined
01:08:00  * marshall_lawchanged nick to marshall_afk
01:09:22  * lyaunzbequit (Ping timeout: 265 seconds)
01:16:56  * towskiquit (Remote host closed the connection)
01:18:27  * lyaunzbejoined
01:20:28  * motiooonjoined
01:20:40  * motiooonquit (Client Quit)
01:36:12  * therealkoopajoined
01:36:55  * therealkoopaquit (Remote host closed the connection)
01:41:54  * admcquit (Quit: Leaving.)
01:52:58  * joshonthewebjoined
01:53:27  * generalissimojoined
02:03:07  * ohamaquit (Remote host closed the connection)
02:03:47  * benv_quit (Quit: Computer has gone to sleep.)
02:10:19  * _ritchquit (Remote host closed the connection)
02:11:45  * benv_joined
02:11:49  * julian_duquejoined
02:16:07  * coderarity-operajoined
02:16:30  <coderarity-opera>hmm
02:18:26  <coderarity-opera> :|
02:23:12  <coderarity>meh
02:24:31  * andris9joined
02:24:54  * c4milojoined
02:24:58  * thl0joined
02:26:08  * kmiller308joined
02:26:53  <kmiller308>hey, I had a question about getting socket.io to work on nodejitsu
02:27:13  <coderarity>hi
02:27:15  <coderarity>what's up?
02:28:18  <kmiller308>i just set up an account, tried to deploy my app, but im getting a 'cannot find module socket.io' error on my server.js file
02:28:25  <kmiller308>im new to node.js so im not sure what im doing
02:28:55  <kmiller308>i have socket.io in a node_modules folder in the same directory that I deployed
02:29:04  <coderarity>check out http://package.json.jit.su - you need to add "socket.io": "0.9.x" to your package.json
02:29:09  * andris9quit (Ping timeout: 248 seconds)
02:29:27  <kmiller308>ill try it out, thanks!
02:29:46  <coderarity>nodejitsu doesn't deploy the node_modules folder, it uses the package.json to install the dependencies into the package.json later
02:30:09  <coderarity>i mean, into the package later
02:30:42  * wookiehangoverquit (Ping timeout: 264 seconds)
02:31:02  * benv_quit (Quit: Computer has gone to sleep.)
02:33:17  * wookiehangoverjoined
02:34:25  <kmiller308>that worked, thanks a lot!
02:34:31  <coderarity>np
02:34:44  * kmiller308quit (Quit: Page closed)
02:38:37  * mdedetrichquit (Quit: ["Textual IRC Client: www.textualapp.com"])
02:40:01  * thl0quit (Remote host closed the connection)
02:41:28  * julian_duquequit (Quit: Lost terminal)
02:51:59  * admcjoined
02:58:37  <Raynos>http-proxy question time!
02:58:51  <coderarity>alright
02:59:57  <Raynos>how do I rewrite urls?
03:00:09  <coderarity>can change req.url
03:00:40  <coderarity>before you call that proxyRequest function
03:00:41  <Raynos>is that going to rewrite it cleanly?
03:00:51  <Raynos>proxyRequest will read req.url and proxy to that?
03:00:54  <coderarity>ceanly?
03:01:00  <coderarity>it will forward that
03:01:03  <coderarity>so it should be fine
03:01:25  <Raynos>ok
03:02:13  * martin___joined
03:02:35  * lwicksjoined
03:04:29  <martin___>hi guys, I have connection errors to my site, can someone please look at this. Here is the gist: https://gist.github.com/4192336 Looks like a loadbalancer issue, right?
03:05:07  <coderarity>that means that your application is refusing the connection to the load balancer, check `jitsu logs`
03:05:26  <martin___>coderity I checked jitsu logs, those requests that fail don't show up there.
03:05:37  * Nodejitsu-Githubjoined
03:05:37  * Nodejitsu-Githubpart
03:05:49  <coderarity>martin___: yeah, they won't, that's what the balancer is saying
03:06:04  <martin___>coderarity and how does that help me?????
03:06:18  <coderarity>martin___: what's your username and appname?
03:06:24  <martin___>modeista modeista-site
03:10:30  * thepumpkinjoined
03:14:45  * jlankjoined
03:15:54  * jlankquit (Remote host closed the connection)
03:16:50  <coderarity>martin___: just `jitsu deploy` again, database document is being weird
03:16:59  <coderarity>martin___: or even just `jitsu start` should fix it
03:18:02  <martin___>coderarity ok. This is a HUGE problem though, you guys need to run some permanent sanity checks. My server monitoring did not catch it for whatever reasons, and we are sending out 10K emails next week.
03:19:10  * Nodejitsu-Githubjoined
03:19:11  * Nodejitsu-Githubpart
03:19:42  * marshall_afkchanged nick to marshall_law
03:20:25  * davidbanhamquit (Remote host closed the connection)
03:21:14  <coderarity>martin___: we're working on bugs as we encounter them, if there's nothing in `jitsu logs` when you see an ECONNREFUSED just come in here, and you can `jitsu start` to fix it and have someone look at the last version of the couch document to figure out what happened
03:24:26  * c4miloquit (Remote host closed the connection)
03:24:40  * blakmatrix1joined
03:25:11  * andris9joined
03:28:19  <martin___>coderarity Those kind of errors could be proactively found by nodejitsu - just run sanity checks over the databases. Same goes when a running site is suddenly down. This needs to be actively monitored by nodejitsu and some action should be taken, like automatic restarting. The financial risk is just to high and it gives nodejitsu a bad rep.
03:29:41  * andris9quit (Ping timeout: 255 seconds)
03:31:01  <Sly>martin___: we don't just do anything because something errors. We'd rather see the error and fix it than ignore it and hope it eventually goes away.
03:31:11  <coderarity>martin___: moving forward we'll be adding things to keep the platform more stable
03:31:42  <Sly>An ECONNREFUSED doesn't necessarily mean something is wrong with our service. It could easily be an app error. So it's not plausible to run a check to automatically restart every ECONNREFUSED drone.
03:32:17  <coderarity>Sly: he means, check if drones.length > maxDrones
03:32:22  <coderarity>Sly: which is what happened in this case
03:32:41  <coderarity>i mean, it's possible to scan the database for maxDrones > drones and `jitsu start`, but there could be unforseen side-effects
03:32:45  <Sly>But that's what caused the ECONNREFUSED, right?
03:33:02  <coderarity>Sly: in this case, the extra two drones were empty, so it caused an ECONNREFUSED as well
03:33:12  <coderarity>that's one reason, but this is the first time I've seen something like this
03:33:38  <coderarity>martin___: ^ we can't fix problems before we see them either :D
03:33:47  <coderarity>martin___: but I assure you we are trying our best
03:34:04  * thepumpk_joined
03:36:34  <martin___>coderarity - I know. It's just a lot at stake for us.
03:37:38  * thepumpkinquit (Ping timeout: 245 seconds)
03:37:38  <coderarity>martin___: people who were already connected without an ECONNREFUSED shouldn't have been affected
03:37:56  <coderarity>martin___: some new people may have gotten an ECONNREFUSED though
03:38:25  <coderarity>martin___: since the balancers have sticky sessions, those who didn't get ECONNREFUSED should have been fine
03:38:33  * michaelmartinezjoined
03:42:33  <martin___>codearity thx.
03:43:42  * jmar777quit (Remote host closed the connection)
03:44:03  * davidbanhamjoined
03:44:22  * martin____joined
03:45:02  <coderarity>martin___: btw, everyone should be fine now, that was just what was happening before - now that you ran `jitsu start`, it's all good
03:45:28  <martin____>coderarity Actually, the sticky load balancer is another problem: It makes it impossible for us to do server monitoring because it always hits the good drone. Any ideas how this could be circumvented? Maybe an http header to prevent sticky sessions in LB
03:45:44  <coderarity>that's a good point
03:46:42  * martin___quit (Ping timeout: 245 seconds)
03:46:49  <coderarity>martin____: there's nothing right now, but that's a good idea
03:46:57  * jlankjoined
03:47:58  <martin____>ok, need to leave. good by everybody
03:48:54  * joshonthewebquit (Quit: Computer has gone to sleep.)
03:52:08  * martin____quit (Ping timeout: 245 seconds)
03:53:29  * st_lukejoined
03:54:18  * jlankquit (Ping timeout: 245 seconds)
04:01:05  <konklone>hi
04:01:12  <konklone>is there an issue with hiredis on nodejitsu?
04:01:34  <coderarity>yes, actualy
04:01:40  <coderarity>you'll have to disable it
04:01:42  <konklone>dang
04:01:51  <konklone>ah, I found this https://github.com/mranney/node_redis/issues/258
04:01:51  <coderarity>the javascript parser is faster anyways
04:01:58  <konklone>how is that possible?
04:02:10  <coderarity>the cost of binding C to javascript is a lot, and the redis protocol is simple
04:03:04  <konklone>I suspect that's true under some conditions and not others?
04:03:42  <mmalecki>it's actually faster for all the cases
04:12:31  <Daniel__>how do we sessions with nodejitsu ?
04:12:36  * malkomalkoquit (Remote host closed the connection)
04:13:21  <coderarity>konklone: JIT rocks
04:13:39  <konklone>huh
04:13:44  <konklone>so why doesn't the hiredis project just shut down
04:14:00  <mmalecki>because it's a generic C library used by different clients
04:14:08  <konklone>got it
04:14:38  <coderarity>konklone: it'd be faster for something like lua, which is interpreted
04:14:56  <coderarity>unless you do luajit, which is dang fast
04:16:09  <konklone>well that was helpful, thank you
04:18:33  * AvianFluquit
04:19:43  <mmalecki>pleasure :)
04:21:44  * jlankjoined
04:21:51  <konklone>question - sometimes, during a deploy to a 2-drone app, it seems like only one of them is up
04:22:01  <konklone>and I don't know if it's one of the new ones being made, or one of the old ones being replace
04:22:05  <konklone>*replaced
04:22:23  <konklone>what is the behavior of the deploy process? I know it's advertised as 0 downtime
04:22:54  <mmalecki>how can you tell that only one is up?
04:23:08  <mmalecki>if you hit them from the web, you'll only ever hit one
04:23:21  <mmalecki>because of sticky sessions
04:23:36  <mmalecki>when you try from a different IP, you might hit the second one
04:23:39  <konklone>I will show you, in a second
04:23:44  <mmalecki>thank you :)
04:24:01  <konklone>although, given traffic right now, I won't be able to prove it
04:24:02  <mmalecki>also, yeah, zero downtime. we first spawn a new drone and then stop the old one
04:24:18  <konklone>it might be better to examine this in more detail during the day on a weekday when I have more traffic
04:24:28  <mmalecki>konklone: what you can do is a simple reporting
04:24:40  <mmalecki>like, when drone is started it sends an http request to a host
04:25:02  <mmalecki>and then the host reports it somehow
04:25:24  <konklone>yeah I have logentries integrated
04:25:49  * andris9joined
04:27:05  <konklone>okay, yeah, I will see what it looks like with a very steady flow of traffic tomorrow
04:27:15  <mmalecki>great, hit me up
04:27:17  <konklone>right now I don't have enough users to consistently generate websockets connections at any given time across both of my drones
04:27:35  * paulbrunojoined
04:28:16  <konklone>I spent today rolling my own redis integration on sockjs so that I can see connected users across all drones
04:28:20  <konklone>http://iic_sockets_staging.jit.su/dashboard shows them
04:28:28  <konklone>(page refreshes every 5s)
04:28:32  <konklone>I only have 2 drones
04:28:35  <konklone>and meager websockets traffic
04:28:42  <konklone>but it'll be neat to see tomorrow
04:28:52  <mmalecki>word :)
04:28:53  * jlankquit (Ping timeout: 245 seconds)
04:29:08  <mmalecki>I just saw some connections to the second drone
04:29:14  <konklone>yeah they are both up and running
04:29:24  <mmalecki>oh, any chance for seeing code for that app?
04:29:27  <konklone>yep
04:29:30  <mmalecki>it's pretty neat actually
04:29:41  <konklone>repo is here - https://github.com/isitchristmas/sockets/
04:29:48  <konklone>relevant stuff is the main app - https://github.com/isitchristmas/sockets/blob/master/app.js
04:29:52  <konklone>and the redis interaction - https://github.com/isitchristmas/sockets/blob/master/redis.js
04:30:16  <konklone>I just hit the point today where my code got large enough that I'm detecting the beginnings of spaghettification
04:30:20  * andris9quit (Ping timeout: 255 seconds)
04:30:40  <mmalecki>very cool thing
04:30:43  <mmalecki>starred
04:30:44  <konklone>oh and all the client side stuff is here - https://github.com/isitchristmas/web/blob/master/views/index.html
04:31:24  <mmalecki>almost like it's christmas XD
04:31:25  <konklone>that app (web) is responsible for finding the country code (IP -> code in MongoDB) and rendering the main index.html template with the code present
04:31:29  <konklone>:)
04:31:41  <mmalecki>loving the readme
04:31:47  <mmalecki>"CODE"
04:31:53  <konklone>:)
04:34:06  <mmalecki>I'm going to sleep but feel free to hit me up tomorrow
04:34:09  <mmalecki>thanks!
04:35:22  <konklone>thanks man, catch you later
04:36:35  * joshonthewebjoined
04:38:25  * cendrizzijoined
04:40:00  * paulbrunoquit (Remote host closed the connection)
04:40:17  <cendrizzi>Hi all. Is there some magic to getting socket.io communication working. I've been only doing local host development so it's all been working great. I can do the initial connection (which is just plain http unless I'm mistaken) but after that no communication. I have comcast as my provider, not sure if they are known to firewall web sockets. It's a mac, no firewall locally.
04:40:54  <konklone>cendrizzi: does any communication fire between the client and the server when deployed?
04:41:02  <konklone>(I'm not a nodejitsu employee)
04:41:05  <cendrizzi>Not after the initial connection
04:41:27  <coderarity>cendrizzi: should be fine - make sure you're connecting on port 80, and you're listening on only 1 port (socket.io can listen on an HTTP server)
04:41:27  <konklone>nodejitsu's proxies proxy websockets automatically
04:41:29  <cendrizzi>I have a little CLI program that uses node to connect. It connections. Then nothing both ways
04:41:41  <cendrizzi>Port 80?
04:41:44  <konklone>you're not doing it in the browser?
04:41:46  <cendrizzi>Or another port
04:42:19  <cendrizzi>Long story, but I'm using the socket.io client software and running from CLI.
04:42:29  <cendrizzi>I can test from browser too. One sec
04:42:46  <coderarity>cendrizzi: connect to it at port 80 from your client, but your server can listen on whatever port
04:42:52  <cendrizzi>Wait a sec, that gave me an idea. just one sec
04:42:55  <coderarity>because the server port will redirect to port 80
04:43:08  * malkomalkojoined
04:43:26  * ravivmgquit (Quit: ravivmg)
04:43:42  <konklone>coderarity: I think I have a zombie drone running from a whole bunch of deploys ago
04:44:01  <konklone>it's posting to my logentries account in a log format I abandoned this morni ng
04:44:16  <coderarity>konklone: can you give me a guess on how many ago? like, no more than 10 ago, or something like that?
04:44:25  <konklone>lemme see
04:44:35  <coderarity>i have to shuffle back through docs and it'd be nice to know when i've gone too far :\
04:45:05  <konklone>okay - I have done 7 deploys today
04:45:18  <coderarity>cool, thanks
04:45:21  <konklone>it's probably one of the first 2 or 3 of those last 7 deploys
04:45:40  <coderarity>awesome
04:45:53  <konklone>here are the 7 in my jitsu output if it helps
04:45:54  <konklone>https://gist.github.com/5a7caecbba4d4926a1b4
04:46:06  * coderarity-operapart
04:46:28  <coderarity>konklone: oh, username/appname too?
04:48:06  <konklone>ah sorry
04:48:19  <konklone>username: konklone appname: sockets-staging
04:49:21  <coderarity>nah, my bad
04:51:28  * malkomalkoquit (Ping timeout: 250 seconds)
04:53:54  <cendrizzi>coderarity: Got it working! Kind of embarrassing. I came here as a last resort and it turns out I was using the wrong url :(.
04:54:35  <coderarity>cendrizzi: :P
04:54:51  <cendrizzi>Doesn't port 80 present issues for web sockets? I've read 443 is much better (firewalls expect encryption and won't do packet inspections). Any way to do that with nodejitsu.
04:54:53  <cendrizzi>?
04:54:54  <coderarity>/names
04:54:56  <coderarity>lol
04:55:15  <coderarity>cendrizzi: i think you can use 443 with secure websockets
04:55:50  <cendrizzi>I guess I was just wondering with nodejitsu and their loadbalancers.
04:56:02  <konklone>I assume nodejitsu supports SSL connections over 443 of all kinds
04:56:04  * jlankjoined
04:56:12  <cendrizzi>Yeah, true.
04:56:48  <cendrizzi>I will have to figure out that another time. Thanks for your help, it helped jog my mind in the right place
05:03:34  <konklone>coderarity: I gotta sign off for the night
05:03:48  <coderarity>konklone: okay, i'll find it and kill it, it just takes time :O
05:04:05  <konklone>no problem man, I appreciate it
05:04:18  * jlankquit (Ping timeout: 245 seconds)
05:07:16  * andris9joined
05:08:31  * prabakaranquit (Quit: Page closed)
05:09:34  * vroquit
05:11:00  * st_lukequit (Remote host closed the connection)
05:22:23  * L10njoined
05:23:01  <L10n>hello all, anyone here have experience with http-proxy?
05:24:18  <coderarity>yeah, what's up L10n
05:25:09  <L10n>having some trouble, server logic is working, unless it's within a callback from a redis function
05:25:28  <L10n>im doing some logic on the request, looking up a value from redis and then trying to proxy the request
05:25:35  * gerredjoined
05:25:41  <L10n>thinking it's a variable scoping issue but not sure
05:26:00  * andris9quit (Remote host closed the connection)
05:28:24  <coderarity>L10n: can I see the code?
05:28:36  * justicefriesquit (Ping timeout: 265 seconds)
05:28:41  <L10n>ya sec to the githubs!
05:30:18  <L10n>https://gist.github.com/6291bf83aef70c767e8a
05:30:53  <L10n>starts at 108
05:30:59  * jlankjoined
05:32:56  <L10n>if i take that request, and dont use the redis calls. works fine
05:36:00  <coderarity>L10n: ah, check this out https://github.com/nodejitsu/node-http-proxy#setup-a-stand-alone-proxy-server-with-latency-eg-io-etc
05:37:02  <L10n>ah so it's timing out?
05:38:10  <coderarity>L10n: the problem is that the redis is an asynchronous operation, so you'll lose data events from the request, unless you buffer that into somewhere and use it later
05:38:24  <L10n>gotcha let me mess with it
05:38:26  <L10n>very helpful
05:38:28  <coderarity>so whenever you have those asynchronous operations, you need to buffer it
05:38:30  <L10n>great lib by the way :D
05:41:34  * jlankquit (Ping timeout: 260 seconds)
05:42:13  * bradleymeckjoined
05:45:20  <L10n>coderarity: im a bit stumped on where i should start refactoring this to support buffer
05:45:58  <coderarity>oh, it's easy
05:46:15  <L10n>var buffer = httpProxy.buffer(req);
05:46:29  <L10n>im assuming i cant just do that in my createServer callback
05:47:17  <coderarity>https://gist.github.com/1e6e6c3b055edd634fbb/02c5ec1df6c5574ddbb2d046bd0721a7315bcdc2 added two lines
05:47:34  <coderarity>line 113, and line 154
05:47:52  <coderarity>L10n: oh, you can, you can have multiple 'data' listeners
05:49:08  <L10n>hmm, i had the same additions you made. still no go.
05:49:56  <coderarity>L10n: what's happening when you make the request?
05:50:20  <L10n>not getting a response
05:50:24  <L10n>not seeing the request
05:50:46  <coderarity>L10n: so you're not even seeing the 'connection from' thing?
05:51:19  <L10n>ah, sorry, yes i see the request at the proxy. just not seeing it at the server behind the proxy.
05:51:43  <L10n>destination host and port are set correctly
05:52:09  <coderarity>L10n: does the /generate path work?
05:52:14  <L10n>yep
05:52:17  <L10n>and /dl
05:52:22  * standoojoined
05:52:29  <L10n>staring up a packet capture
05:52:30  * standoopart
05:52:32  * Daniel__quit (Ping timeout: 245 seconds)
05:52:34  <L10n>to see if anything is coming in
05:52:55  <coderarity>oh, that's because I was totally wrong
05:53:24  <coderarity>i think
05:54:13  <L10n>not seeing any tcp connections to the server behind the proxy
05:54:28  <coderarity>check out line 156, https://gist.github.com/1e6e6c3b055edd634fbb
05:55:01  * admcquit (Quit: Leaving.)
05:55:26  * admcjoined
05:56:43  <L10n>so sick :D
05:56:45  <L10n>it's working
05:56:58  <coderarity>:D
05:57:25  <L10n>but uhh, yeah very cool module. this is rad.
05:57:36  <L10n>scalable shells
05:58:20  <coderarity>for redis?
05:59:31  <L10n>well im using redis to track somethings
05:59:45  <L10n>but this is for metasploit. i work as a security consultant. and wanted to reverse proxy some shells
06:00:12  <coderarity>i see
06:00:46  <coderarity>L10n: by "security consultant" do you mean "ninja who breaks into people's stuff and gets paid for it"?
06:01:03  <L10n>i try :)
06:01:30  <L10n>but yeah, that's how we roll
06:04:18  <L10n>i was looking to build something, so when we exploit workstations, our shells can come back to single ip and port.
06:05:01  <coderarity>sounds intense
06:05:32  <coderarity>like one of those CIA shows where they break into a computer
06:06:35  <L10n>except real, and it's just me looking at a terminal
06:06:51  <L10n>i enjoy 'hacking' on code more than running tools tho :)
06:07:23  <coderarity>L10n: also there probably aren't a bunch of people coming to kill you
06:07:27  <coderarity>which might reduce the intensity
06:07:29  <coderarity>but only slightly
06:08:06  * jlankjoined
06:14:07  * defunctzombiechanged nick to defunctzombie_zz
06:14:13  <L10n>:)
06:14:40  * _sorensenquit (Quit: _sorensen)
06:14:44  * michaelmartinezquit (Quit: Check it, Wreck it http://www.caffeineindustries.com/blog)
06:18:28  * jlankquit (Ping timeout: 245 seconds)
06:19:27  * cendrizziquit (Quit: cendrizzi)
06:26:30  * andris9joined
06:27:06  * bradleymeckquit (Quit: bradleymeck)
06:31:18  * andris9quit (Ping timeout: 264 seconds)
06:31:41  * cendrizzijoined
06:34:10  * sreeixjoined
06:45:48  * jlankjoined
06:48:05  * towskijoined
06:49:29  <gildean>L10n: i built one such app, that gets the clients to make a reverse-connection: http://julkinen.salaliitto.com/misc/porter.png
06:50:03  <gildean>L10n: the client connects towars the server with https-post-actions, gets some info and then connects with websockets
06:50:41  <gildean>then you can use that c&c view to execute commands, or open reverse-ssh-tunnels with one the buttons
06:56:48  * jlankquit (Ping timeout: 245 seconds)
07:09:29  <L10n>gildean: very cool. did you release it?
07:10:17  <gildean>not yet, i haven't had time to clean out the code
07:10:32  <gildean>i'll try and do that this week and release the stuff
07:10:46  <L10n>cool, mind mailing me when you're done?
07:10:59  <gildean>i was thihking about adding the vnc-implementation substacks has written, so you can get a remote dektop as well
07:11:19  <gildean>L10n: i don't know about mailing, but i can give you a shout here in irc
07:11:20  <L10n>what is the client written in?
07:11:28  <gildean>the client is node too
07:11:35  <L10n>alright, hopefully I am around?
07:11:38  <gildean>that way not very easy to just drop it
07:11:42  <L10n>err disregard that ? :D
07:12:37  <gildean>it'll prolly be here on my github account: https://github.com/gildean
07:12:55  <L10n>k cool, ill follow it. was looking there before i asked.
07:14:59  * toonketelsjoined
07:17:17  * cendrizziquit (Quit: cendrizzi)
07:21:13  <L10n>really glad i stumbled into the node community, you guys have some crazy projects.
07:23:13  <gildean>imo node.js is a great enabler
07:23:24  * jlankjoined
07:23:46  <gildean>it enables you to start doing something you didn't previously think you had the time or the skills to do
07:23:54  <L10n>gildean: well put
07:24:13  <L10n>it's been a bit of a learning curve moving from other languages to javascript
07:24:25  <L10n>but im catching on. is there a go to resource for learning the "right" way to do things?
07:25:21  <gildean>well, most of the time when i'm writing js i try to follow crockfords conventions: http://javascript.crockford.com/code.html
07:25:55  <L10n>bookmarked ty
07:26:24  <L10n>gildean: think im having trouble with the most is how the code flows. im used to have functions that return something.
07:26:44  <gildean>you can have functions return something in node too
07:26:56  <gildean>either straight away, or in the callback
07:27:07  <L10n>lemme think of an example
07:27:11  <coderarity>L10n: you can do whatever you want, just use callbacks and asynchronous operations <- that's the "node.js" part
07:27:15  <coderarity>L10n: also use javascript
07:27:25  <coderarity>;P
07:27:37  <gildean>you can have a function like this: function giveMeObject() { return { this: "is an object" }};
07:28:03  <L10n>say i have funcion a, that calls an async function b. how does b return to a that then returns to the caller
07:28:14  <L10n>as of now ive been using counters
07:29:06  <gildean>or like var giveMeObjectWhenready = function (callback) { var obj = { this: "is an object }; callback(obj); };
07:29:09  <coderarity>L10n: that's actually a good point, objects are awesome - like yo can do function setup (options) {} and just have options be an object, and call it like setup({ option1: 'value'})
07:29:40  <coderarity>L10n: also, it's generally a good idea to avoid constructors - like var o = createObject() rather than var o = new Object()
07:32:26  <gildean>L10n: in that case i'd prolly use nested callbacks
07:32:49  <L10n>gildean: right, that's what ive been doing
07:33:01  <gildean>so when the callback of function b is called with the results, then just call the callback of the first function
07:33:02  <L10n>which is where my brain had to so some work
07:34:54  * jlankquit (Ping timeout: 264 seconds)
07:36:53  <gildean>the most i usually have to work is to make sure i don't create refs to things that get changed or discarded so that an open ref is left there
07:37:07  <gildean>as in, memory leaks
07:38:11  * ohamajoined
07:39:46  * Swaagiejoined
07:44:27  * towskiquit (Remote host closed the connection)
07:45:20  * blakmatrixquit (Remote host closed the connection)
07:45:38  * blakmatrix1quit (Quit: Leaving.)
07:46:52  * wilsonpagejoined
07:48:15  <wilsonpage>Hey guys, anyone able to help me with a deploy error?
07:48:16  <wilsonpage>https://gist.github.com/605cb5a1cb66a37316b7
07:49:17  * davidbanhamquit (Remote host closed the connection)
07:50:30  * FrenkyNetquit (Quit: Computer has gone to sleep.)
07:51:38  <coderarity>wilsonpage: looking
07:53:27  * `3rdEdenjoined
07:55:35  <coderarity>wilsonpage: hmmm, can you give it another try?
07:55:52  <wilsonpage>Sure
07:56:02  <coderarity>wilsonpage: also might need to do `jitsu config set timeout 1000000`
07:56:14  * Nodejitsu-Githubjoined
07:56:14  <Nodejitsu-Github>[jitsu] mmalecki pushed 1 new commit to master: http://git.io/BSVIkQ
07:56:14  <Nodejitsu-Github>jitsu/master 74a62b3 Maciej Małecki: [dist] Bump version to 0.11.4
07:56:14  * Nodejitsu-Githubpart
07:57:31  * alucardXjoined
07:57:37  * travis-cijoined
07:57:38  <travis-ci>[travis-ci] nodejitsu/jitsu#255 (master - 74a62b3 : Maciej Małecki): The build passed.
07:57:38  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/2f7fc03c567d...74a62b3bbc17
07:57:38  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/3471789
07:57:38  * travis-cipart
07:58:56  <wilsonpage>@coderarity Still not luck I'm afraid, should I up the timeout?
07:59:08  <wilsonpage>PS. How do I mention people on this thing?
07:59:26  <coderarity>leave out the @
07:59:28  <coderarity>just like
07:59:35  <coderarity>coderarity: hi! and stuff
07:59:49  <wilsonpage>coderarity: ah ok :)
07:59:56  <coderarity>wilsonpage: if you mean private message, it's /msg <username> <message>
08:00:45  <coderarity>wilsonpage: yeah, up the timeout and i'll see if there's anything in logs again
08:00:55  <gildean>or open up a query with /query <username>
08:01:30  * jlankjoined
08:01:36  <gildean>wilsonpage: also, name completion works with tab
08:01:52  <gildean>so you only need to type the first letter of the name and press tab
08:02:15  * Nodejitsu-Githubjoined
08:02:15  <Nodejitsu-Github>[jitsu] mmalecki pushed 1 new commit to master: http://git.io/UG_LiA
08:02:15  <Nodejitsu-Github>jitsu/master 396d646 Maciej Małecki: [api] Remove useless config directives
08:02:15  * Nodejitsu-Githubpart
08:02:36  <wilsonpage>gildean: Wow that is cool thanks :)
08:03:07  <wilsonpage>coderarity: Upped the timeout, eating now, but hanging...
08:03:11  <wilsonpage>*waiting
08:03:14  * andris9joined
08:03:32  * travis-cijoined
08:03:32  <travis-ci>[travis-ci] nodejitsu/jitsu#256 (master - 396d646 : Maciej Małecki): The build passed.
08:03:32  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/74a62b3bbc17...396d646232eb
08:03:32  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/3471835
08:03:32  * travis-cipart
08:03:54  <coderarity>wilsonpage: yeah, didn't have to wait as long before because it was hanging up before it was completed
08:04:09  <wilsonpage>What are peoples favourite IRC groups for JS and front end related stuff?
08:04:13  <coderarity>it's probably going to be an error based on the drones i'm checking, but we'll fix things one step at a time
08:04:29  <coderarity>wilsonpage: some people go to ##javascript, but I don't
08:04:42  <wilsonpage>coderarity: Why not?
08:05:30  <coderarity>eh, i don't quite like the general attitude
08:06:03  <coderarity>it's actually not so bad, I just don't have a good enough reason to continue staying there
08:06:20  <coderarity>i used to hang out in #node.js too, but it's pretty crowded and a lot of it is just questions
08:06:23  <wilsonpage>coderarity: Fair snuff, any groups you can recommend?
08:07:04  <coderarity>wilsonpage: tbh, anything other than node and javascript i've done isn't website related, so that's all I've got :D
08:07:26  <gildean>we have some random web-devs at #webtech, you're welcome to join
08:07:31  * generalissimoquit (Remote host closed the connection)
08:07:43  <coderarity>wilsonpage: there's also a search function in IRC
08:07:44  <wilsonpage>coderarity: Thanks, this may open up a whole realm of newness for me :)
08:07:52  <gildean>not strictly a help-channel or anything, but people do share ideas there etc.
08:08:25  <gildean>for more help-related there's #web, which has some ok people
08:08:40  <coderarity>wilsonpage: if you're hanging around on freenode a lot, probably worth it to read http://freenode.net/philosophy.shtml
08:08:51  <coderarity>freenode itself is a community just as the IRC channels it contains
08:08:51  <wilsonpage>coderarity: Ah thank you!
08:09:14  <wilsonpage>coderarity: So nice to have someone actually explain IRC!
08:09:53  <coderarity>wilsonpage: register your nickname, too. /msg chanserv help
08:09:56  <coderarity>ooops
08:10:00  * mappumquit (Ping timeout: 260 seconds)
08:10:02  <coderarity>wilsonpage: i mean, /msg nickserv help
08:10:14  <wilsonpage>coderarity: What does that do?
08:10:23  <coderarity>wilsonpage: makes it so no one steals your nickname
08:10:47  <gildean>wilsonpage: also some channels require you to be registerd and authed to join
08:11:14  <gildean>particulary if the channel suffers from flooders etc.
08:13:14  * jlankquit (Ping timeout: 260 seconds)
08:14:08  <wilsonpage>coderarity: Same error happening on jitsu I'm afraid :(
08:14:52  <wilsonpage>coderarity: Nickname registered, thanks!
08:17:18  <coderarity>wilsonpage: can I see your package.json?
08:20:15  * FrenkyNetjoined
08:20:19  * dob_joined
08:21:57  <wilsonpage>Sure
08:23:02  <wilsonpage>coderarity: https://gist.github.com/8e67649b0c0f756c5d6e
08:23:12  <coderarity>thanks
08:23:27  <wilsonpage>This is an app that has been running for a good few months, then went down last week
08:23:58  <wilsonpage>coderarity: I tried to restart it and that failed, so I tried starting it again, and this is where I am
08:24:19  <coderarity>i see
08:24:34  <coderarity>well, there's a problem on the drone, but we're looking at it
08:24:54  <wilsonpage>coderarity: Ah ok
08:25:27  <wilsonpage>coderarity: I'm going to cycle to work now, but will be on this for the next few hours.
08:25:37  <coderarity>okay, cool
08:32:37  * wilsonpagequit (Quit: wilsonpage)
08:39:37  * jlankjoined
08:44:50  <booyaa>morning chaps
08:45:32  <coderarity>hi
08:50:58  * jlankquit (Ping timeout: 245 seconds)
08:52:52  * yyolkquit (Read error: Connection reset by peer)
08:54:01  * davidbanhamjoined
08:55:08  * yyolkjoined
09:03:53  * coderarityquit (Remote host closed the connection)
09:13:15  * davidbanhamquit (Remote host closed the connection)
09:15:04  * kaarealjoined
09:15:40  * coderarityjoined
09:17:45  * MannyCaljoined
09:18:17  * jlankjoined
09:18:42  * kaarealquit (Remote host closed the connection)
09:19:00  * admcquit (Quit: Leaving.)
09:20:41  * stokejoined
09:20:56  <nathan7>Hey coderarity
09:21:03  <coderarity>hi
09:21:04  <nathan7>How's this lovely morning in coderarity-land?
09:22:07  <coderarity>pretty good
09:22:37  <coderarity>except every time i do one of those mini-games where you have to not choose 1 of the things being shuffled, I always watch the bad one and get confused and grab it, lol
09:22:49  <nathan7>heh
09:23:01  <nathan7>hmm
09:25:35  <mmalecki>oh shit. http://jvectormap.com/
09:25:55  <mmalecki>I... I know what I'm going to do
09:25:59  <mmalecki>this will be fucking epic
09:26:17  <mmalecki>EVERYONE STAND BACK I KNOW SCIENCE
09:29:18  * jlankquit (Ping timeout: 245 seconds)
09:33:52  <nathan7>mmalecki: this is gonna end badly
09:34:45  <mmalecki>dtrace is involved.
09:35:11  <nathan7>..yep.
09:36:24  <mmalecki>it also involves SSH'ing into production machines
09:37:04  * nathan7puts hazmat suit on
09:37:16  <nathan7>everyone loves hazmat suits, amirite
09:37:26  <mmalecki>yup.
09:38:48  * cjmquit (Remote host closed the connection)
09:40:02  <coderarity>nathan7: i think you underestimate the danger
09:40:20  * coderaritybuilds and stocks a bomb shelter
09:40:25  <mmalecki>coderarity: be prepared to save the cloud if I accidentally it
09:40:43  <nathan7>not on his chronometer
09:42:15  <coderarity>mmalecki: don't tell me - `pkgin rm node` on all the drones?
09:43:00  <mmalecki>it's worse.
09:44:10  <coderarity>mmalecki: you're good at solaris, right? can it run X11?
09:45:27  <mmalecki>it can
09:45:46  <mmalecki>in fact, you can run GNOME on some of them
09:46:36  <coderarity>cool
09:47:08  <coderarity>now i just need to learn how to write my own graphics card drivers
09:47:16  <coderarity>and then i can totally use solaris at home
09:47:58  <nathan7>heh
09:48:49  <mmalecki>okay, got the map, now to integrate it...
09:57:04  * jlankjoined
10:05:18  * toonketelsquit (Read error: Connection reset by peer)
10:05:37  * wilsonpagejoined
10:05:45  * toonketelsjoined
10:06:59  * kaarealjoined
10:07:22  * thepumpk_quit (Ping timeout: 250 seconds)
10:08:28  * jlankquit (Ping timeout: 245 seconds)
10:11:13  * kaarealquit (Ping timeout: 256 seconds)
10:15:12  * evangenieurjoined
10:16:12  * kaarealjoined
10:16:57  * thepumpk_joined
10:20:25  * kaarealquit (Remote host closed the connection)
10:20:57  * kaarealjoined
10:25:08  * kaarealquit (Ping timeout: 245 seconds)
10:26:35  * vhost-supportjoined
10:26:58  <vhost-support>Hi, one simply question
10:27:19  <vhost-support>Does nodejitsu support connect.vhost features?
10:27:37  <vhost-support>thanks for support
10:27:48  * thepumpk_quit (Remote host closed the connection)
10:28:20  <booyaa>vhost-support: quirky nick you got there
10:31:45  * thepumpkinjoined
10:32:28  <coderarity>vhost-support: looks like it
10:32:39  <coderarity>vhost-support: as long as you are only listening on 1 port
10:33:03  <vhost-support>thanks coderarity
10:33:14  <vhost-support>I will try
10:35:32  * jlankjoined
10:47:38  * jlankquit (Ping timeout: 245 seconds)
10:47:48  <nathan7>I need to write a bug report for Plates today
10:49:18  * drinchevjoined
10:50:26  <drinchev>Hello, I was wondering how to activate the option for free SSL on *.nodejitsu.com ?
10:50:37  <drinchev>I tried depolying my app with custom generated certificates
10:51:10  <drinchev>but it gives an error : "(35) Unknown SSL protocol error in connection to"
10:52:06  <gildean>drinchev: it shouldn't need anything
10:52:39  <gildean>there is a reverse-proxy in front that terminates the https-connection
10:52:46  <gildean>so it should just work
10:53:26  <gildean>unless your server is using https as well
10:53:43  <gildean>i'm not sure if the reverse-proxy does https to https proxying
10:54:03  <drinchev>I want my server to be forced to https only
10:54:10  <drinchev>this is my app.coffee file :
10:54:16  <drinchev>options = key: fs.readFileSync('ssl/key.pem'), cert: fs.readFileSync('ssl/cert.pem')
10:54:21  <drinchev>https = require 'https'
10:54:32  <drinchev>https.createServer(options, app).listen 443
10:54:55  <gildean>yeah, someone from nodejitsu has to answer to the question about https to https proxying
10:54:59  * cjmjoined
10:55:12  * booyaaquit (Read error: Operation timed out)
10:55:37  <coderarity>drinchev: just redirect from HTTP -> HTTPS
10:55:49  <coderarity>drinchev: you have to create your server as an HTTP server
10:55:54  <coderarity>but your users can access it as HTTPS
10:55:59  <coderarity>the load balancers will handle that
10:56:24  <coderarity>drinchev: if you want to use your own SSL files, check out https://ssl.jit.su - but it's going to require a business plan in the future
10:56:33  <gildean>drinchev: also you can check the url for protocl with the url-module
10:56:53  <coderarity>drinchev: check out http://headers.jit.su to figure out if users are connected with HTTP
10:57:03  <coderarity>"x-forwarded-proto"
10:58:19  <drinchev>okay thanks, I'll check this out.
10:58:52  <drinchev>Is there an example for basic file-serving https nodejitsu-deployed server somewhere in github ?
10:59:14  * malkomalkojoined
10:59:23  * booyaajoined
11:00:28  * vhost-supportquit (Ping timeout: 245 seconds)
11:04:25  * toonketelsquit (Remote host closed the connection)
11:04:41  <gildean>drinchev: node-static works well
11:04:42  <gildean>imo
11:04:59  * thepumpkinquit (Remote host closed the connection)
11:05:55  * YoYquit (Quit: Leaving...)
11:06:17  <L10n>anybody ever see ntlm http authentication in node?
11:06:23  <L10n>as a client
11:13:38  * stagasjoined
11:13:44  * _yoy_joined
11:14:30  * jlankjoined
11:14:39  <drinchev>10x guys it worked ...
11:25:13  * marciopugajoined
11:25:46  <marciopuga>hello?
11:26:47  <gildean>ehlo
11:26:48  * jlankquit (Ping timeout: 245 seconds)
11:31:56  * marciopugaquit (Remote host closed the connection)
11:34:27  * cesconixjoined
11:37:05  * evangenieurquit (Remote host closed the connection)
11:37:31  * evangenieurjoined
11:42:12  * evangenieurquit (Ping timeout: 264 seconds)
11:53:23  * jlankjoined
11:56:18  * drinchevquit (Ping timeout: 245 seconds)
11:58:54  * ralphtheninjaquit (Quit: Lost terminal)
12:04:43  * jlankquit (Ping timeout: 245 seconds)
12:08:40  <booyaa>L10n: trying to auth through a ISA proxy so your node script can access the web?
12:09:25  <booyaa>L10n: you'll need a NTLM proxy (CNTLM), i don't think i've seen anything native for node yet.
12:15:25  * kaarealjoined
12:17:47  * jamesjwoodjoined
12:22:19  * jamesjwood_joined
12:23:55  <wilsonpage>coderarity: Any news?
12:24:51  * cjm__joined
12:24:52  <coderarity>wilsonpage: give it another shot and let me know if it's still happening
12:25:18  * cjmquit (Ping timeout: 264 seconds)
12:26:14  * toonketelsjoined
12:26:17  * jamesjwoodquit (Ping timeout: 245 seconds)
12:26:18  * jamesjwood_changed nick to jamesjwood
12:26:18  <wilsonpage>coderarity: Curretnly hanging on 'start'
12:26:58  * thl0joined
12:27:35  <gildean>wilsonpage: you're sure your app works locally?
12:28:05  <wilsonpage>I have made no changes since last deploy
12:28:12  <wilsonpage>Should I try a deploy?
12:28:14  <L10n>booyaa: actually, im trying to guess passwords on a sharepoint server real fast
12:28:24  <coderarity>it's socket hang up-ing because it's taking forever, and that's happening because of some other problem
12:28:29  <coderarity>wilsonpage: yeah, deploy
12:28:53  <L10n>booyaa: didnt see anything native either
12:29:32  <wilsonpage>coderarity: https://gist.github.com/259c7501322f9200920f
12:30:14  <coderarity>wilsonpage: the fact that you see `npm install` output there is very concerning
12:30:28  <coderarity>wilsonpage: but you should deploy, even if there aren't code changed
12:30:33  <coderarity>ohhhh, I know what happened!
12:30:53  <coderarity>something change since last time you started, and now that you are `jitsu start`ing that old snapshot again, it's incompatible
12:30:57  <coderarity>and a deploy will fix that
12:31:34  * stagasquit (Quit: ChatZilla 0.9.89-rdmsoft [XULRunner 1.9.0.17/2009122204])
12:31:54  * jlankjoined
12:32:54  <wilsonpage>coderarity: https://gist.github.com/a9142fdee2ee90f7d1f8
12:33:27  <coderarity>wilsonpage: `jitsu start`
12:34:27  * gerredquit (Quit: Leaving...)
12:34:30  <wilsonpage>https://gist.github.com/0c69996c250f18f1a008
12:34:39  <wilsonpage>coderarity: https://gist.github.com/0c69996c250f18f1a008
12:35:45  <coderarity>maybe update express-expose? and maybe node version update? i don't really know, that's a problem from inside your app
12:36:02  <coderarity>do `npm install` and then try running it locally again
12:36:30  <coderarity>and i'll free my desktop
12:40:32  * kaarealquit (Remote host closed the connection)
12:41:06  * kaarealjoined
12:43:03  * jlankquit (Ping timeout: 245 seconds)
12:45:12  * malkomalkoquit (Read error: Connection reset by peer)
12:45:14  * kaarealquit (Ping timeout: 244 seconds)
12:45:47  * malkomalkojoined
12:48:01  * kaarealjoined
12:49:37  * kaarealquit (Remote host closed the connection)
12:50:04  * FrenkyNetchanged nick to FrenkyNet|work
12:55:16  * redir_joined
12:55:47  * redirquit (Disconnected by services)
12:55:47  * redir_changed nick to redir
12:56:27  * relurkjoined
13:01:22  <jamesjwood>hello, anyone available to help with a deployment error
13:01:54  <booyaa>L10n: why not wireshark it? you probably don't need node if that's all you're after
13:03:41  * evangenieurjoined
13:04:05  <coderarity>jamesjwood: what's up?
13:05:36  * dob_quit (Remote host closed the connection)
13:06:18  * retrofoxjoined
13:07:05  * FrenkyNet|workquit (Quit: ["Textual IRC Client: www.textualapp.com"])
13:10:16  * jlankjoined
13:18:56  * dob_joined
13:20:11  * jmar777joined
13:22:32  * julian_duquejoined
13:22:38  * jlankquit (Ping timeout: 245 seconds)
13:23:01  * fentjoined
13:33:51  * lwicksquit (Ping timeout: 260 seconds)
13:35:19  * therealkoopajoined
13:37:16  * thl0quit (Remote host closed the connection)
13:44:56  <Sly>Everyone doing okay in here?
13:47:42  <konklone>mmalecki: http://mapbox.com/ is also a terrific product - though tile based and not vector
13:49:17  * jlankjoined
13:49:19  <wilsonpage>coderarity: Thanks I'll have to wait till I get home to try it locally
13:57:58  * konklonequit (Quit: Leaving.)
14:02:04  * jlankquit (Ping timeout: 260 seconds)
14:13:25  * justicefriesjoined
14:20:20  * devdazedjoined
14:25:25  * thl0joined
14:25:30  * wesbosjoined
14:26:24  * FrenkyNetjoined
14:28:19  * jlankjoined
14:33:08  * toonketelsquit (Remote host closed the connection)
14:34:23  * ralphtheninjajoined
14:35:07  * toonketelsjoined
14:38:49  * jlankquit (Ping timeout: 260 seconds)
14:40:31  * c4milojoined
14:41:07  * justicefriesquit (Quit: Leaving...)
14:43:28  * evangenieurquit (Remote host closed the connection)
14:43:55  * evangenieurjoined
14:44:29  * defunctzombie_zzchanged nick to defunctzombie
14:47:29  * malkomalkoquit (Remote host closed the connection)
14:48:45  * evangenieurquit (Ping timeout: 260 seconds)
14:51:05  * evangenieurjoined
14:58:28  * mdedetrichjoined
15:01:07  * bradleymeckjoined
15:02:06  * sreeixquit (Quit: sreeix)
15:05:50  * jlankjoined
15:06:51  * FrenkyNetquit (Quit: Computer has gone to sleep.)
15:10:45  * retrofoxquit (Ping timeout: 256 seconds)
15:15:58  * jlankquit (Ping timeout: 245 seconds)
15:17:19  * Destosjoined
15:20:44  * andris9quit (Remote host closed the connection)
15:21:06  * kenperkinsquit (Quit: Computer has gone to sleep.)
15:24:01  * anoemijoined
15:24:11  * cronopiojoined
15:30:07  * Destosquit (Quit: Destos)
15:30:27  * Destosjoined
15:31:53  * jlankjoined
15:33:49  <evangenieur>is there a way to get more than 256Mb per instances ? it's really short
15:34:27  * cjm__changed nick to cjm
15:35:01  * sirkitreejoined
15:37:28  * malkomalkojoined
15:39:46  <Sly>evangenieur: not to my knowledge.
15:40:02  <Sly>(changing RAM)
15:42:09  * jmar777quit (Remote host closed the connection)
15:44:34  <mmalecki>evangenieur: nope, not yet.
15:45:25  * mdedetrichquit (Quit: Computer has gone to sleep.)
15:46:15  * FrenkyNetjoined
15:47:10  * generalissimojoined
15:49:23  * sreeixjoined
15:49:24  * alucardXquit (Quit: leaving)
15:54:10  <evangenieur>:(
15:57:55  * defunctzombiechanged nick to defunctzombie_zz
15:58:16  * cendrizzijoined
16:03:18  * paulbrunojoined
16:05:59  * wilsonpagequit (Quit: wilsonpage)
16:07:48  * vrojoined
16:10:08  * jmar777joined
16:10:52  * anoemiquit (Quit: anoemi)
16:11:32  * Swaagiequit (Quit: Ik ga weg)
16:13:53  * fentquit (Quit: leaving)
16:16:51  <fearphage>cronopio: i pushed a few pull requests
16:17:07  <fearphage>I'm working on adding tests for rackspace also
16:17:54  <cronopio>Fearphage thank you so much i will review asap
16:18:44  * switzjoined
16:19:56  * cendrizziquit (Quit: cendrizzi)
16:21:00  * cendrizzijoined
16:21:25  * evangenieurquit (Remote host closed the connection)
16:21:51  * evangenieurjoined
16:22:27  * kwhinneryjoined
16:23:28  * switzquit (Ping timeout: 245 seconds)
16:26:36  * evangenieurquit (Ping timeout: 264 seconds)
16:28:13  * c4miloquit (Remote host closed the connection)
16:28:18  * kenperkinsjoined
16:34:50  * jacob4u2joined
16:34:59  * retrofoxjoined
16:41:04  * nrw1joined
16:41:33  * nrw1quit (Client Quit)
16:42:06  * nrw1joined
16:42:31  * dob__joined
16:42:36  * kwhinneryquit (Quit: kwhinnery)
16:43:19  * bardujoined
16:43:23  * julian_d1quejoined
16:44:17  * julian_d1quequit (Client Quit)
16:44:41  * evangenieurjoined
16:47:00  * frankdejongejoined
16:47:46  * barduquit (Ping timeout: 250 seconds)
16:48:19  * lyaunzbequit (Ping timeout: 260 seconds)
16:49:18  * nrw1quit (Quit: Leaving.)
16:49:36  * nrw1joined
16:50:56  * FrenkyNetquit (*.net *.split)
16:50:56  * sirkitreequit (*.net *.split)
16:50:57  * julian_duquequit (*.net *.split)
16:50:57  * dob_quit (*.net *.split)
16:50:59  * frankdejongechanged nick to FrenkyNet
16:51:21  * sirkitreejoined
16:51:46  * lesbosjoined
16:51:47  * nrw1quit (Read error: Connection reset by peer)
16:52:20  * wesbosquit (Disconnected by services)
16:52:24  * lesboschanged nick to wesbos
16:53:23  * toonketelsquit (Remote host closed the connection)
16:53:47  * slloydjoined
16:55:54  * anoemijoined
16:56:34  * konklonejoined
16:58:01  * julian_duquejoined
16:58:11  <fearphage>cronopio: i have a bunch of tests that i want to get merged separately from the fixes. the other way is i send a massive blob of changes in many files. suggestions?
16:58:35  * cendrizziquit (Quit: cendrizzi)
16:59:59  <cronopio>You can create separate pull requests
17:00:17  <fearphage>but they are dependent
17:00:27  <fearphage>i guess i'll merge from the branch where the tests exist
17:00:51  <cronopio>Ok
17:01:18  <fearphage>or i can let you cherry pick
17:01:53  <cronopio>I will cherry-pick anyway
17:05:08  * indexzerojoined
17:05:14  * zz_shykeschanged nick to shykes
17:05:29  * MannyCalquit (Quit: Page closed)
17:07:04  <fearphage>cronopio: lib/pkgcloud/core/storage/file.js File.prototype.download = .... this.client.upload(...); that's a typo, right? or is it too early in the morning for me?
17:07:46  <cronopio>Yeah shoud be a typo
17:07:55  <fearphage>cool. i'll push that too
17:08:19  * martin_joined
17:10:59  <konklone>coderarity: did you end up finding that zombie drone? it is still reporting in to my logentries account
17:11:15  <konklone>there've been a couple more deploys since then, I can give you a new estimate of where it is if you need
17:11:49  * admcjoined
17:12:22  * slloydquit (Read error: Connection reset by peer)
17:13:20  * switzjoined
17:13:45  * Nodejitsu-Githubjoined
17:13:45  * Nodejitsu-Githubpart
17:13:53  * AvianFlujoined
17:14:03  <fearphage>cronopio: there you go
17:14:09  <fearphage>pull request 51
17:14:56  <konklone>I have a question about SSL encryption for websockets
17:15:00  <cronopio>Awesome! Thank you
17:15:42  <konklone>People say it improves the chance of connection by convincing proxies/routers/etc to not deep packet inspect it
17:16:12  <konklone>I am a little concerned about the computational expense and latency of encrypting all the packets running up and down the wire
17:16:40  <konklone>especially when I don't actually need security, and especially don't need the more expensive (but standard) type of SSL encryption that guarantees forward secrecy
17:17:03  <konklone>I would be fine if my SSL packets were encrypted via rot13 :)
17:17:05  * slloydjoined
17:17:11  <CoverSlide>konklone: do you have a source for these people?
17:17:41  <konklone>sure - here is an (old - Jan 2010) set of numbers from Google about Chrome - http://www.ietf.org/mail-archive/web/tls/current/msg05593.html
17:17:51  <gildean>some application firewalls do block unsecure websocket-connections
17:17:55  <CoverSlide>maybe there are routers that don't understand protocol upgrades
17:18:11  <CoverSlide>hmm
17:18:26  <konklone>yeah - I'm trying to find the other links I read, but that was the gist of it
17:18:41  * toonketelsjoined
17:18:46  * Nodejitsu-Githubjoined
17:18:46  * Nodejitsu-Githubpart
17:18:49  <konklone>that the HTTP-esque requests that Websockets make are foreign enough to most routers that look at packets that they get rejected
17:19:01  * stagasjoined
17:19:04  <gildean>solution: use node-http-proxy in front to terminate the ssl-connection
17:19:11  <gildean>works great with websockets too
17:19:20  <CoverSlide>well it's not very performant to have your application do the https, usually that's best delegated to an external proxy
17:19:28  <gildean>that way the encryption workload is on the proxy and not the app
17:19:29  <CoverSlide>like node-http-proxy
17:19:35  <konklone>right, which in this case is Nodejitsu's node-http-proxy
17:19:52  <gildean>or what ever you want
17:20:08  <konklone>but it's still extra expense and latency
17:20:13  <konklone>I'm using this to do mouse movement sharing
17:20:14  <CoverSlide>there's also bouncy, which is nice because it uses raw sockets instead of going through http
17:20:17  <gildean>but with nodejitsu you can just use the proxy that's there already
17:21:04  <gildean>konklone: the latency it creates is miniscule, at least after the initial connection
17:21:23  <Sly>gildean: how are you doing?
17:21:46  <konklone>gildean: really? that is unintuitive, since I am transferring many packets very fast, as mice move
17:21:54  <gildean>Sly: just fine, how about you?
17:22:02  <konklone>I would expect that running every single packet through a solid SSL algorithm would slow it down noticeably
17:22:23  <Sly>I'm good. :D
17:23:21  <gildean>konklone: well, at least in my experience the added latency is not noticeable
17:23:26  <gildean>konklone: why not try?
17:24:00  <gildean>if your app is on nodejitsu, you can just change the websocket-address in the clientside js to point to wss://whatever.nodejitsu.com
17:24:22  <gildean>instead of just ws://
17:24:43  <gildean>the proxy will automatically handle the ssl-termination
17:26:02  <konklone>OK, I will try :)
17:26:20  <konklone>I'll need to buy a cert to avoid a browser warning though, right?
17:26:49  * evangenieurquit (Remote host closed the connection)
17:27:12  <gildean>iirc the nodejitsu.com and jit.su domains should have a wildcard cert, but if you're using your own domain, then yes
17:27:16  * evangenieurjoined
17:27:20  <konklone>got it
17:27:28  <gildean>or rather, the wss connection won't be made if the cert is not trusted
17:27:35  <konklone>*nods*
17:27:40  <gildean>i won't give an error besides "can't connect"
17:27:42  * ircretaryquit (Ping timeout: 276 seconds)
17:31:04  * Nodejitsu-Githubjoined
17:31:05  * Nodejitsu-Githubpart
17:32:04  * evangenieurquit (Ping timeout: 260 seconds)
17:33:48  * ralphtheninjaquit (Ping timeout: 264 seconds)
17:36:09  * wilsonpagejoined
17:36:27  * indexzeroquit (Quit: indexzero)
17:38:05  * julian_duquequit (Ping timeout: 256 seconds)
17:38:30  <fearphage>seems like rackspace storage is not popular among the node cirlces
17:39:29  * cronopioquit (Read error: Connection reset by peer)
17:39:30  * FrenkyNetquit (Quit: Computer has gone to sleep.)
17:39:49  * paulbrunoquit (Remote host closed the connection)
17:40:11  * cronopiojoined
17:45:58  * cronopioquit (Quit: Bye)
17:46:11  * switzpart ("Linkinus - http://linkinus.com")
17:46:26  * cronopiojoined
17:47:21  * _sorensenjoined
17:49:11  * shykeschanged nick to zz_shykes
17:51:06  <wilsonpage>coderarity: Got it all up and running again thanks!
17:52:20  <wilsonpage>coderarity: It was a combination of something your end, and non-specific dependency versions in my package.json
17:53:28  * thepumpkinjoined
17:55:51  * _ritchjoined
17:55:55  * dob_joined
17:57:06  * thl0quit (Remote host closed the connection)
17:58:35  * shamajoined
17:59:37  * dob__quit (Ping timeout: 245 seconds)
18:01:53  * towskijoined
18:02:07  * sirkitreequit (Ping timeout: 265 seconds)
18:02:27  * lyaunzbejoined
18:08:09  * lpinjoined
18:09:09  * jlankquit (Remote host closed the connection)
18:09:39  * dob_quit (Remote host closed the connection)
18:10:05  * dob_joined
18:10:38  * jlankjoined
18:11:31  * kwhinneryjoined
18:12:14  * kwhinnery_joined
18:12:20  * toonketelsquit (Remote host closed the connection)
18:14:11  * BrandonMLjoined
18:14:37  * sirkitreejoined
18:14:46  * blakmatrixjoined
18:14:58  * thepumpkinquit (Remote host closed the connection)
18:15:30  * zz_shykeschanged nick to shykes
18:15:48  * dob_quit (Ping timeout: 264 seconds)
18:15:58  * kwhinneryquit (Ping timeout: 245 seconds)
18:15:58  * kwhinnery_changed nick to kwhinnery
18:16:55  * admcquit (Quit: Leaving.)
18:17:17  * blakmatrix_joined
18:18:25  * julian_duquejoined
18:19:25  * bradleymeckquit (Quit: bradleymeck)
18:22:49  * toonketelsjoined
18:23:20  * TooTallNatejoined
18:25:03  * st_lukejoined
18:25:14  * gouldingjoined
18:25:59  * `3rdEdenquit (Remote host closed the connection)
18:26:14  <goulding>having some trouble deploying my app. this always seems intermittent - this time its a RackSpace Error (404): Item not found
18:26:35  <yawnt>goulding: hey, that's usually rackspace being slow
18:26:56  <goulding>so I just keep trying?
18:26:59  <yawnt>you should check if your snapshot was uploaded with `jitsu snapshots list` and then activate it.. that usually does the trick
18:27:39  <goulding>ok trying that
18:29:25  <goulding>is webops running slowly too? Maybe this is an issue on my end, but web ops won't even get to the login screen after about 30s...
18:29:37  <lpin>i have unusual latency on websockets connections
18:29:46  <lpin>testing on http://wsping.jit.su/
18:29:59  <lpin>got spike of 1k
18:30:03  <lpin>spikes*
18:30:13  <lpin>is it just me?
18:31:54  <goulding>even http://handbook.jitsu.com is slow for me
18:32:47  * `3rdEdenjoined
18:32:53  * benvjoined
18:33:33  * npmbroquit (Ping timeout: 246 seconds)
18:34:08  * npmbrojoined
18:34:57  <mmalecki>joyent appears to be having some problems, we're looking into it
18:35:12  * toonketelsquit (Remote host closed the connection)
18:35:23  <lpin>mmalecki ok thanks for the info :)
18:35:33  * mmaleckitopic: Nodejitsu - Host applications. Keep them up. | Cloud Status: seeing increased latency across the cloud. We're investigating.
18:36:18  * gouldingquit (Ping timeout: 245 seconds)
18:38:11  * mmaleckitopic: Nodejitsu - Host applications. Keep them up. | Cloud Status: upstream provider issues are causing increased latency. We're investigating.
18:38:14  * thl0joined
18:38:28  * npmbroquit (Ping timeout: 245 seconds)
18:38:44  <sberryman>lovely, love how you guys are on top of it already (pingdom just went crazy on me)
18:39:17  * TooTallNatequit (Ping timeout: 256 seconds)
18:41:24  * gouldingjoined
18:42:00  * TooTallNatejoined
18:42:49  * jmar777quit (Remote host closed the connection)
18:43:11  * c4milojoined
18:44:24  <mmalecki>seeing lower latency, packet loss rate 0 %
18:44:42  <mmalecki>there are still latency spikes but issue appears to be resolved
18:46:41  * cesconixquit (Quit: Textual IRC Client: www.textualapp.com)
18:48:15  <mmalecki>load balancer latency is back to normal
18:49:10  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:49:13  * mmaleckitopic: Nodejitsu - Host applications. Keep them up. | Cloud Status: Joyent might be experiencing packet loss, but things seem fine on our end: https://help.joyent.com/entries/22556848-packet-loss-latency-in-east-1-datacenter
18:49:13  * shamaquit (Quit: shama)
18:49:50  * mappumjoined
18:53:40  * julian_duquequit (Quit: Lost terminal)
18:54:08  * thepumpkinjoined
18:54:27  * julian_duquejoined
18:55:01  * shamajoined
18:55:41  * malkomalkoquit (Remote host closed the connection)
18:57:02  * TooTallNatequit (Read error: Connection reset by peer)
18:57:31  * TooTallNatejoined
19:01:41  * bradleymeckjoined
19:04:09  * admcjoined
19:07:04  * thepumpk_joined
19:07:21  * coderarityquit (Quit: back to sleeping)
19:07:58  * joshonthewebjoined
19:08:07  * swaagiejoined
19:10:20  * thepumpkinquit (Ping timeout: 250 seconds)
19:11:18  * martin_quit (Ping timeout: 245 seconds)
19:14:10  * st_lukequit (Remote host closed the connection)
19:14:37  * gouldingquit (Ping timeout: 245 seconds)
19:18:32  <sberryman>mmalecki: all looks good for me as well.. was having some serious issues for about 10-12 minutes
19:19:08  <mmalecki>yeah, that's what we've been seeing too
19:19:21  <mmalecki>at some point packet loss was about ~50 %
19:20:46  * andris9joined
19:22:27  * jlankquit (Remote host closed the connection)
19:30:44  * jlankjoined
19:31:57  * malkomalkojoined
19:35:30  * stagasquit (Quit: ChatZilla 0.9.89-rdmsoft [XULRunner 1.9.0.17/2009122204])
19:35:35  * malkomal_joined
19:37:08  * malkomal_part
19:40:54  * jmar777joined
19:41:51  * defunctzombie_zzchanged nick to defunctzombie
19:45:06  * lpinquit (Ping timeout: 264 seconds)
19:45:49  * toonketelsjoined
19:47:39  * lyaunzbequit (Ping timeout: 260 seconds)
19:50:36  * toonketelsquit (Ping timeout: 264 seconds)
19:54:05  * sirkitreechanged nick to sirkitree|lunch
19:55:26  <Sly>Everyone doing okay in here?
19:56:16  * paulbrunojoined
19:57:00  * indexzerojoined
19:57:38  * benvquit (Quit: Computer has gone to sleep.)
19:58:06  * lpinjoined
20:00:38  * switzjoined
20:01:02  * retrofoxquit (Ping timeout: 250 seconds)
20:01:52  * lyaunzbejoined
20:02:32  * sirkitree|lunchquit (Read error: Connection reset by peer)
20:03:03  * Sly_joined
20:05:32  <konklone>Sly_: I'm doing okay
20:06:23  * Slyquit (Ping timeout: 245 seconds)
20:09:43  * TooTallNatequit (Ping timeout: 265 seconds)
20:10:22  * TooTallNatejoined
20:17:15  * Sly_changed nick to Sly
20:21:23  * `3rdEdenquit (Remote host closed the connection)
20:21:46  * paulbrunoquit (Remote host closed the connection)
20:23:27  * indexzeroquit (Quit: indexzero)
20:25:44  * benvjoined
20:28:16  * paulbrunojoined
20:29:23  * towskiquit (Remote host closed the connection)
20:29:44  * `3rdEdenjoined
20:31:21  * switzquit (Quit: Leaving...)
20:32:25  * jmar777quit (Remote host closed the connection)
20:34:22  * jmar777joined
20:37:10  * Nodejitsu-Githubjoined
20:37:10  <Nodejitsu-Github>[jitsu] mmalecki pushed 3 new commits to master: http://git.io/J3O3sw
20:37:10  <Nodejitsu-Github>jitsu/master 4f901ba stammen: added .idea to ignore Webstorm IDE files
20:37:10  <Nodejitsu-Github>jitsu/master 0418be2 stammen: bumped vows version to 0.7.x so tests will run on windows
20:37:10  <Nodejitsu-Github>jitsu/master b04a5cc Maciej Małecki: Merge pull request #366 from MSOpenTech/windows-fix...
20:37:10  * Nodejitsu-Githubpart
20:38:20  * FrenkyNetjoined
20:47:31  <Sly>Everyone still doing alright?
20:47:45  <konklone>Sly: I am so good right now
20:47:49  * paulbrunoquit (Remote host closed the connection)
20:47:55  <Sly>Good deal.
20:48:26  * `3rdEdenquit (Remote host closed the connection)
20:49:45  * switzjoined
20:52:55  * indexzerojoined
20:57:38  * papachanjoined
20:59:45  * Slyquit (Remote host closed the connection)
20:59:57  * davidbanhamjoined
21:00:53  * jmar777quit (Read error: Connection reset by peer)
21:01:19  * jmar777joined
21:01:34  <anoemi>Sly: I AM NOT OK
21:01:46  <anoemi>lolwait. never mind. i'm fine.
21:04:26  * stokequit (Quit: Sto andando via)
21:04:27  * sreeixquit (Quit: sreeix)
21:05:09  <mmalecki>related: http://xkcd.com/222/
21:06:09  * sirkitree|lunchjoined
21:06:42  <anoemi>mmalecki: awesome <3
21:07:33  * paulbrunojoined
21:09:04  * stokejoined
21:09:06  * benvquit (Ping timeout: 264 seconds)
21:10:21  * benvjoined
21:11:25  <paulbruno>Can I ask a Twitter/ntwitter-related question? (Not sure about protocol here. And be forewarned, I'm a professional programmer/JS developer, but a Node noob.)
21:12:11  <paulbruno>(This is my first time, btw. On this IRC channel/server.)
21:13:56  * sirkitree|lunchchanged nick to sirkitree
21:14:21  <blakmatrix>paulbruno: you may
21:14:36  <paulbruno>Thanks.
21:15:00  <paulbruno>Trying to use the login method of the ntwitter module, to get user authorization.
21:16:15  <paulbruno>Seems to work well, and even checked the cookies for a test account, showing what I can only assume are a valid access token and secret for that particular user, but all calls to the convenience methods, like verifyCredidentials or updateStatus, get a Twitter error code returned.
21:16:30  <paulbruno>HTTP status 400, Twitter API error code 215.
21:16:40  <paulbruno>Which is basically "Bad authentication data."
21:16:42  <Leeol>Question: If i recall correctly, jitsu will increment by package number on each publish, correct? Is there anyway i can make it *not* do this, and instead overwrite the build if it's the same build?
21:17:25  <Leeol>The reason for this is that if there is a build process error i don't want to have to lose parity between my code base version and what is uploaded on jitsu. Does that make sense?
21:17:40  <blakmatrix>paulbruno: most likely this is due to the new twitter api and ntwitter needing a refactor, it hasnt been updated in a while
21:18:29  <paulbruno>blakmatrix: Oh, okay. What's that? I'm somewhere in-between novice and intermediate in my Twitter API knowledge, and that applies for OAuth as well.
21:18:36  * benvquit (Quit: Computer has gone to sleep.)
21:18:50  <paulbruno>blakmatrix: Oh, refactor, as in the entire module.
21:18:52  * travis-cijoined
21:18:53  <travis-ci>[travis-ci] nodejitsu/jitsu#258 (master - b04a5cc : Maciej Małecki): The build passed.
21:18:53  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/396d646232eb...b04a5cc22625
21:18:53  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/3483154
21:18:53  * travis-cipart
21:19:03  <paulbruno>Or, at least the auth piece.
21:19:29  <blakmatrix>Leeol: Afraid not, we have plans in the future for that but it's not implemented yet
21:19:42  <Leeol>blakmatrix: Ok :/
21:22:22  <Leeol>blakmatrix: Out of curiosity, is that feature on any sort of timeframe? Or is it just on the board/list?
21:23:10  <paulbruno>blakmatrix: One other question/statement, though... concerning ntwitter.
21:24:26  <paulbruno>blakmatrix: When I pre-specify, on the ntwitter object's instantiation, the pre-generated access token and key for the Twitter account that owns the app, and then I try to perform the exact same Twitter API calls through the module, they work fine.
21:24:53  <paulbruno>blakmatrix: So, I guess this would suggest that it's something about the login method, and the way it gets the access tokens/keys?
21:26:27  <blakmatrix>Leeol: its is just on a board atm, it should get quickly addressed once we move away from using rackspace cloudfiles.
21:26:46  <Leeol>Also, is there an npm hook (such as npm's `prepublish`) for pushing to jitsu? (to automate build processes)
21:26:54  <Leeol>blakmatrix: k, thanks for the info :)
21:27:43  <blakmatrix>paulbruno: that sounds about right, I know AvianFlu has been talking about possibly sometime soon updating the app
21:27:58  * BrandonMLquit (Ping timeout: 245 seconds)
21:28:23  * Nodejitsu-Githubjoined
21:28:23  * Nodejitsu-Githubpart
21:28:24  * konklonequit (Ping timeout: 264 seconds)
21:28:43  <blakmatrix>Leeol: yes "predeploy" , checkout http://package.json.jit.su/
21:28:53  <Leeol>blakmatrix: ty again
21:29:11  <paulbruno>blakmatrix: Okay. Maybe, in my ADD, I'll see about rolling a fix of my own, and putting in a pull request if I get that lucky and I write it that well.
21:29:35  <paulbruno>blakmatrix: Thanks for your help.
21:29:37  * stokequit (Quit: Leaving)
21:29:48  * stokejoined
21:29:53  * jlankquit (Remote host closed the connection)
21:32:25  * benvjoined
21:33:26  * andris9quit (Remote host closed the connection)
21:34:39  * jmar777quit (Remote host closed the connection)
21:36:29  * FrenkyNetquit (Quit: Computer has gone to sleep.)
21:38:49  * lyaunzbequit (Ping timeout: 260 seconds)
21:39:23  * yyolkquit (Quit: yyolk)
21:44:02  * mdedetrichjoined
21:47:06  * konklonejoined
21:47:54  * switzquit (Quit: Leaving...)
21:53:47  * mdedetrichquit (Quit: Computer has gone to sleep.)
21:55:19  * stagasjoined
22:01:31  * jmar777joined
22:03:00  * lyaunzbejoined
22:03:55  * stokequit (Quit: Leaving)
22:08:52  * Slyjoined
22:15:04  * wesbosquit (Quit: Leaving...)
22:15:52  * wilsonpagequit (Quit: wilsonpage)
22:16:52  * vroquit (Ping timeout: 248 seconds)
22:21:12  * bradleymeckquit (Quit: bradleymeck)
22:27:01  * yyolkjoined
22:27:34  * papachanquit (Quit: Saliendo)
22:28:03  * lyaunzbequit (Quit: leaving)
22:28:44  * lyaunzbejoined
22:34:12  * lpinquit (Quit: Leaving)
22:34:13  * andris9joined
22:35:21  * Nodejitsu-Githubjoined
22:35:22  * Nodejitsu-Githubpart
22:36:02  * kwhinneryquit (Quit: kwhinnery)
22:38:17  * julian_duquequit (Quit: leaving)
22:38:55  * andris9quit (Ping timeout: 260 seconds)
22:40:09  * sylisjoined
22:40:15  <sylis>hi
22:41:57  <sylis>how many drones is required to handle ~1000 socket.io connections ?
22:42:35  <blakmatrix>sylis: concurrent would be 2-3
22:42:42  * benvquit (Quit: Computer has gone to sleep.)
22:44:14  <sylis>thanks
22:45:00  * Powderhoundjoined
22:46:17  <sylis>I'm not sure if it's the right place to ask but with more than one drone do I need to use a redisStore for socket.io ?
22:49:00  * davidbanhamquit (Remote host closed the connection)
22:49:01  * Nodejitsu-Githubjoined
22:49:01  * Nodejitsu-Githubpart
22:51:48  * indexzeroquit (Quit: indexzero)
22:52:56  * TooTallNatequit (Read error: Connection reset by peer)
22:55:43  * jmar777quit (Remote host closed the connection)
22:55:45  * retrofoxjoined
22:57:54  * TooTallNatejoined
22:59:13  * benvjoined
23:00:12  * retrofoxquit (Ping timeout: 264 seconds)
23:01:19  * dob_joined
23:03:31  * retrofoxjoined
23:04:45  * Slyquit (Remote host closed the connection)
23:04:54  <sylis>how do we manage multi drones with socket.io ?
23:05:12  <AvianFlu>you need a redisStore, as you said
23:05:13  <AvianFlu>yes
23:05:29  <AvianFlu>something to keep track of sessions independent of the drones
23:06:12  * redirquit (Quit: ...)
23:06:13  * relurkchanged nick to redir
23:07:45  * PatFjoined
23:07:53  * PatFquit (Read error: Connection reset by peer)
23:08:09  * mdedetrichjoined
23:10:18  * retrofoxquit (Ping timeout: 264 seconds)
23:10:49  <sylis>Tks AvianFlu, I'll go with iriscouch then :)
23:11:06  * jscjoined
23:11:55  <blakmatrix>irishcouch haha :)
23:11:59  * jacob4u2quit (Quit: Computer has gone to sleep.)
23:12:12  * Destosquit (Ping timeout: 264 seconds)
23:12:46  * retrofoxjoined
23:13:07  <defunctzombie>just to understand clearly, the free github push deployment is just a bonus for open source projects, you still have to pay for a "drone" if you are deploying an open source project right?
23:13:50  <blakmatrix>yes
23:14:33  <defunctzombie>k
23:14:41  <defunctzombie>still very cool :)
23:15:17  * davidbanhamjoined
23:15:37  * Nodejitsu-Githubjoined
23:15:37  <Nodejitsu-Github>[haibu] mmalecki pushed 1 new commit to master: http://git.io/5o5E-A
23:15:37  <Nodejitsu-Github>haibu/master 26396d6 Maciej Małecki: [dist] Fix the test script
23:15:37  * Nodejitsu-Githubpart
23:16:07  * dob__joined
23:18:34  * dob_quit (Ping timeout: 255 seconds)
23:21:03  * swaagiequit (Quit: Leaving)
23:27:06  * konklonepart
23:29:56  * rvaggquit (Quit: ta ta)
23:29:59  * defunctzombiechanged nick to defunctzombie_zz
23:31:12  * anoemiquit (Quit: anoemi)
23:35:02  * andris9joined
23:35:37  * constantxjoined
23:36:46  * Powderhoundquit (Quit: Computer has gone to sleep.)
23:37:06  * constantxpart
23:37:25  * constantxjoined
23:38:07  <constantx>hey guys, I just read about nodejitsu and travis-ci integration, would it work with a private repo?
23:38:29  <constantx>would it be safe since there are sensitive information in that private repo?
23:39:35  * andris9quit (Ping timeout: 260 seconds)
23:39:38  * evangenieurjoined
23:40:10  <fearphage>cronopio: is there a reason you don't click the merge button or some other method that shows it was merged when you take the entire commit?
23:40:18  <fearphage>just curious
23:41:40  * fbergrothjoined
23:42:42  <blakmatrix>fearphage: I was told once merge commits make one look like a greenhorn
23:43:11  <blakmatrix>fearphage: so it might be something to that
23:43:17  * yyolkquit (Quit: yyolk)
23:43:54  * thepumpk_quit (Remote host closed the connection)
23:44:49  * mmoultonjoined
23:44:57  * jmar777joined
23:45:30  <blakmatrix>fearphage: I guess a pretty good article on this is http://gitguru.com/2009/02/03/rebase-v-merge-in-git/
23:46:14  * _ritchquit (Quit: Leaving.)
23:47:47  <mmoulton>Best practices question... what is the best way to support deploying the same repo to multiple drones in nodejitsu? For example to support multiple environments such as dev, stage, prod.
23:48:07  <constantx>mmoulton +1
23:48:22  <mmalecki>constantx: it should work
23:48:30  <mmoulton>Is there a package.json construct for an environment to change the package name / subdomain / etc?
23:49:06  <mmalecki>(private repo, I mean)
23:49:08  <constantx>mmalecki: so my private git will not be exposed via travis-ci in anyway?
23:49:51  <mmalecki>oh, if the project is not on travis we simply won't look for it there
23:52:48  * rvaggjoined
23:54:20  * switzjoined
23:58:28  * generalissimoquit (Remote host closed the connection)
23:59:22  <mmoulton>mmalecki: Does nodejitsu have any thoughts on my best practices question? In how can jitsu best support deploying the same repo to drones to support environments such as dev, stage, prod?