00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:08  * mikljoined
00:00:08  * ircretaryjoined
00:04:42  * tgriesserquit (Remote host closed the connection)
00:05:08  * thealphanerdjoined
00:07:44  * cesconixquit (Quit: Computer has gone to sleep.)
00:08:06  * thl0joined
00:16:45  * thealphanerdquit (Quit: thealphanerd)
00:21:24  * ptetaujoined
00:21:58  <ptetau>is anyone else having trouble using the CLI atm?
00:22:11  <ptetau>I get an error: getaddrinfo ENOTFOUND
00:22:26  * jamundquit (Quit: jamund)
00:22:47  <jcrugzz>ptetau: what were you running?
00:23:04  * admc1quit (Quit: Leaving.)
00:24:03  * rosskquit (Remote host closed the connection)
00:25:31  <ptetau>jitsu deploy
00:26:41  * meso_quit (Read error: Connection reset by peer)
00:26:51  * mesojoined
00:28:43  <ptetau>I've signed out of nodejitsu
00:29:09  <ptetau>then tried to deploy, and it fails just after I enter my password
00:29:49  <kenperkins>twitter fail
00:32:47  * jcrugzz_joined
00:32:57  <jcrugzz_>sry disconnected
00:35:33  * tgriesserjoined
00:36:11  * jcrugzzquit (Ping timeout: 252 seconds)
00:36:33  * miklquit (Quit: Computer has gone to sleep.)
00:41:26  * jcrugzz_changed nick to jcrugzz
00:43:54  * tgriesserquit (Ping timeout: 264 seconds)
00:47:58  * ptetauquit (Ping timeout: 245 seconds)
00:48:25  * thl0quit (Remote host closed the connection)
00:56:24  * nodejitsu-githubjoined
00:56:24  <nodejitsu-github>[system.json] indexzero pushed 1 new commit to master: http://git.io/qlIO4Q
00:56:24  <nodejitsu-github>system.json/master 750eda9 Charlie Robbins: Merge pull request #11 from opsmezzo/clusters...
00:56:24  * nodejitsu-githubpart
00:57:04  * admc1joined
00:57:16  * travis-cijoined
00:57:16  <travis-ci>[travis-ci] opsmezzo/system.json#3 (master - 750eda9 : Charlie Robbins): The build passed.
00:57:16  <travis-ci>[travis-ci] Change view : https://github.com/opsmezzo/system.json/compare/231dccf6a848...750eda9fdf00
00:57:16  <travis-ci>[travis-ci] Build details : http://travis-ci.org/opsmezzo/system.json/builds/7039407
00:57:16  * travis-cipart
00:57:46  * travis-cijoined
00:57:46  <travis-ci>[travis-ci] opsmezzo/quill#11 (master - ac4d54f : Charlie Robbins): The build passed.
00:57:46  <travis-ci>[travis-ci] Change view : https://github.com/opsmezzo/quill/compare/64c581c25eb9...ac4d54f74840
00:57:46  <travis-ci>[travis-ci] Build details : http://travis-ci.org/opsmezzo/quill/builds/7039411
00:57:46  * travis-cipart
00:57:53  <mmalecki>W00T
00:58:13  <jcrugzz>mmalecki: GREAT SUCCESS
00:58:33  * papachanquit (Quit: Leaving)
01:01:47  * Nijikoquit (Read error: Connection reset by peer)
01:02:26  * Nijikojoined
01:05:49  * nodejitsu-githubjoined
01:05:49  <nodejitsu-github>[system.json] indexzero pushed 1 new commit to master: http://git.io/OaMgEg
01:05:49  <nodejitsu-github>system.json/master 72cfedd indexzero: [dist] Version bump. 1.2.2
01:05:49  * nodejitsu-githubpart
01:06:44  * travis-cijoined
01:06:45  <travis-ci>[travis-ci] opsmezzo/system.json#4 (master - 72cfedd : indexzero): The build passed.
01:06:45  <travis-ci>[travis-ci] Change view : https://github.com/opsmezzo/system.json/compare/750eda9fdf00...72cfeddba348
01:06:45  <travis-ci>[travis-ci] Build details : http://travis-ci.org/opsmezzo/system.json/builds/7039572
01:06:45  * travis-cipart
01:06:59  * nodejitsu-githubjoined
01:07:00  <nodejitsu-github>[system.json] indexzero deleted v1.2.2 at 0209d39: http://git.io/-YoVaA
01:07:00  * nodejitsu-githubpart
01:07:14  * nodejitsu-githubjoined
01:07:14  <nodejitsu-github>[system.json] indexzero tagged v1.2.2 at 6cf166f: http://git.io/9vR_4w
01:07:14  * nodejitsu-githubpart
01:07:24  * anoemijoined
01:09:14  * travis-cijoined
01:09:14  <travis-ci>[travis-ci] opsmezzo/quill#12 (master - 5cdb490 : indexzero): The build passed.
01:09:14  <travis-ci>[travis-ci] Change view : https://github.com/opsmezzo/quill/compare/ac4d54f74840...5cdb4907b505
01:09:14  <travis-ci>[travis-ci] Build details : http://travis-ci.org/opsmezzo/quill/builds/7039607
01:09:14  * travis-cipart
01:13:15  * jgablequit (Quit: Computer has gone to sleep.)
01:15:39  * joshonthewebquit (Quit: Computer has gone to sleep.)
01:19:01  * jahaquit (Quit: Leaving.)
01:32:49  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
01:33:07  * joshonthewebjoined
01:33:55  * anoemi_joined
01:35:35  * anoemiquit (Ping timeout: 252 seconds)
01:35:35  * anoemi_changed nick to anoemi
01:37:18  * admc1quit (Quit: Leaving.)
01:40:20  * sirkitree|afkquit (Quit: Textual IRC Client: www.textualapp.com)
01:51:24  * mmaleckichanged nick to mmalecki[zzz]
02:06:48  * admc1joined
02:08:42  * leichtgewichtjoined
02:18:16  * Heboquit
02:23:01  * brianloveswordsquit (Excess Flood)
02:23:22  * brianloveswordsjoined
02:28:09  * jamundjoined
02:34:28  * thealphanerdjoined
02:39:34  * thealphanerdquit (Quit: thealphanerd)
02:43:35  * joshonthewebquit (Quit: Computer has gone to sleep.)
02:44:15  * joshonthewebjoined
02:49:32  * ptetaujoined
02:57:52  * thealphanerdjoined
03:01:10  * jamundquit (Quit: jamund)
03:01:48  * jamundjoined
03:01:55  * admc1quit (Quit: Leaving.)
03:08:23  * ptetauquit (Ping timeout: 245 seconds)
03:10:20  * mokesjoined
03:17:09  * tgriesserjoined
03:24:00  * jamundquit (Quit: jamund)
03:26:09  * chrisdotcode_joined
03:26:48  * chrisdotcodequit (Ping timeout: 245 seconds)
03:29:14  * chrisdotcode_quit (Remote host closed the connection)
03:32:58  * chrisdotcodejoined
03:41:29  * mokesquit (Remote host closed the connection)
03:43:48  * mokesjoined
03:44:56  * tgriesserquit (Remote host closed the connection)
03:51:45  * tgriesserjoined
03:52:11  * tgriesserquit (Remote host closed the connection)
03:52:38  * generalissimojoined
04:00:02  * mokesquit (Remote host closed the connection)
04:08:03  * oinkonquit (Ping timeout: 252 seconds)
04:16:49  * indexzerojoined
04:22:54  * cronopioquit (Ping timeout: 264 seconds)
04:24:41  * Hebojoined
04:26:23  * cronopio[phone]quit (Ping timeout: 245 seconds)
04:32:30  * oinkonjoined
04:32:38  * anoemiquit (Quit: anoemi)
04:34:33  * admc1joined
04:40:25  * standoojoined
04:41:09  <kenperkins>indexzero: how do you guys typically communicate plans for others to see
04:41:24  <indexzero>kenperkins: generally gists
04:41:36  <indexzero>we haven't collaborated with that many big companies
04:41:40  <kenperkins>example of one?
04:41:50  <kenperkins>I'm thinking more to our users, than anyone
04:42:18  <indexzero>this is private, but here: https://gist.github.com/indexzero/8f87c290c072de7e7549
04:42:37  <kenperkins>ah right, ok so just a spec in girst
04:42:39  <kenperkins>ok
04:42:43  <indexzero>yup
04:42:55  <indexzero>if HP comes in we could use something like Trello
04:43:04  <indexzero>we communicate with our users through UserVoice
04:43:12  <indexzero>but that's a little too consumer-y for this
04:44:10  <julianduque>Trello is a very good option, I used it before and it's awesome :)
04:44:21  <kenperkins>yea I'm well versed in trello :P
04:44:57  <indexzero>cool
04:45:02  <indexzero>I didn't know you worked at Clipboard
04:45:06  <indexzero>I know those dudes through FRC
04:45:12  <indexzero>hung out at their offices like a year ago
04:47:55  <kenperkins>seriously?
04:48:03  <kenperkins>I met you there
04:48:08  <kenperkins><-- emp #1 at clipboard
04:48:24  <kenperkins>technically greg mark and I all started day 1, but I accepted first :P
04:51:59  <indexzero>we probably met back then, or maybe you were out of the office that day
04:52:23  <kenperkins>no im certain we met because gary called me into the room with you to talk about our deployment shit with puppet
04:53:28  <kenperkins>I'm just forgettable I suppose :D
04:54:04  * lyetzjoined
04:54:26  * andris9joined
04:56:04  <indexzero>lol, no
04:56:13  <indexzero>kenperkins: FYI https://github.com/nodejitsu/pkgcloud/issues/130
04:56:18  <kenperkins>yea im looking
04:56:22  <indexzero>minor change, you got a few cycles tonight?
04:56:28  <indexzero>just ran into it for this OpenStack setup on my laptop
04:56:35  <kenperkins>does it break you
04:57:01  <kenperkins>rather, is this just an inconsistency, or does it actually have a bug
04:57:11  <indexzero>yeah, and it breaks the purpose of pkgcloud, you can't just pass the same options to every method for every provider
04:57:41  <indexzero>it's just an inconsistency, but inconsistency in options (that are required across all providers) is a bug by definition
04:58:36  * sreeixjoined
04:58:40  <indexzero>e.g. Amazon takes the option of "PublicKeyMaterial", but we just set that from `options.key` || https://github.com/nodejitsu/pkgcloud/blob/master/lib/pkgcloud/amazon/compute/client/keys.js#L68-L73
04:59:14  <indexzero>so I can pass the same options object to Amazon, Azure, Joyent, etc, except (now) OpenStack
04:59:59  <indexzero>funny how minor things become big when you're building a consistent abstraction :)
05:02:19  <kenperkins>so I'm confused, there's only 1 reference to "public_key" anywhere in the project, and it's in a comment: https://github.com/nodejitsu/pkgcloud/blob/master/lib/pkgcloud/openstack/compute/client/keys.js#L32
05:03:00  <kenperkins>are you saying, openstack as an api uses public_key, so we should transform from key to public key in the implementation?
05:03:14  * Nodejitsu-Githubjoined
05:03:14  * Nodejitsu-Githubpart
05:03:26  <indexzero>kenperkins: Yes, that's it exactly
05:03:34  <kenperkins>sorry that was a bit ambiguous
05:03:54  <indexzero>in our higher level provisioning products we do things like
05:03:56  <kenperkins>or im slow
05:04:03  * travis-cijoined
05:04:03  <travis-ci>[travis-ci] nodejitsu/pkgcloud#68 (gh-130 - 1f755ca : indexzero): The build passed.
05:04:03  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/pkgcloud/commit/1f755cae56c6
05:04:03  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/pkgcloud/builds/7043011
05:04:03  * travis-cipart
05:04:22  <indexzero>pkgcloud.compute.createClient(group.provider).addKey(keyOptions)
05:04:31  * Heboquit
05:04:38  <kenperkins>right, I understand
05:04:45  <kenperkins>an abstraction only works when there's consistency
05:04:59  * Hebojoined
05:05:01  <indexzero>cool
05:05:24  <indexzero>kenperkins: Already fixed :) please review https://github.com/nodejitsu/pkgcloud/pull/131
05:05:29  * Nodejitsu-Githubjoined
05:05:29  * Nodejitsu-Githubpart
05:06:02  <kenperkins>pretty benign
05:06:07  <kenperkins>do it
05:06:17  <kenperkins>or did you want me to :D
05:06:29  <indexzero>kenperkins: dooo itttt ;)
05:06:45  <kenperkins>cherry pick for a single commit or just click merge on GH
05:06:46  <indexzero>I'm doing a bunch of OpenStack work tonight, so don't bother version bumping yet, I might find other small things
05:06:59  <kenperkins>i've got some massive branches in progress :S
05:07:08  <indexzero>I usually cp on small things, and hit merge on big things
05:07:11  <kenperkins>ok brb
05:07:14  <indexzero>I'm OK with merge commits when it's major
05:07:20  * zkirilljoined
05:07:37  <kenperkins>how do you cherry pick out of a forked PR?
05:07:45  <kenperkins>(when it's not on jitsu/pkgcloud)
05:09:28  <kenperkins>also, when PR is on nodejitsu/pkgcloud and not a fork, who's responsibility to delete to branch?
05:10:02  * Nodejitsu-Githubjoined
05:10:03  * Nodejitsu-Githubpart
05:10:35  <indexzero>the person who merges or cherry-picks the PR
05:10:38  * mokesjoined
05:10:45  <kenperkins>k brb
05:10:46  <indexzero>also, to CP from not a fork
05:10:53  * travis-cijoined
05:10:53  <travis-ci>[travis-ci] nodejitsu/pkgcloud#70 (master - 0e4b34f : indexzero): The build passed.
05:10:53  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/pkgcloud/compare/f7ae0027a260...0e4b34f1673d
05:10:53  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/pkgcloud/builds/7043101
05:10:53  * travis-cipart
05:10:53  <indexzero>git checkout branch-name
05:10:59  <indexzero>git log # get commit sha
05:11:03  * travis-cijoined
05:11:03  <travis-ci>[travis-ci] rackspace/pkgcloud#63 (master - 0e4b34f : indexzero): The build passed.
05:11:03  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/compare/f7ae0027a260...0e4b34f1673d
05:11:03  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7043104
05:11:03  * travis-cipart
05:11:04  <kenperkins>that's what i did
05:11:05  <indexzero>git cherry-pick SHA
05:11:13  * Nodejitsu-Githubjoined
05:11:13  * Nodejitsu-Githubpart
05:11:15  <indexzero>cool, you got it then ;)
05:11:30  <kenperkins>did you see my inline auth/piping PR
05:13:28  * travis-cijoined
05:13:28  <travis-ci>[travis-ci] rackspace/pkgcloud#64 (raxIdentity - 9feeb80 : Ken Perkins): The build passed.
05:13:28  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/compare/b0ed431e5188...9feeb80866a1
05:13:28  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7043135
05:13:28  * travis-cipart
05:13:36  <kenperkins>pshaw, I should have mentioned: update the comment to not say public_key
05:13:40  <kenperkins>Code Review Fail.
05:13:52  * oinkonquit (Quit: leaving)
05:15:12  * mokesquit (Ping timeout: 264 seconds)
05:24:01  * Heboquit
05:25:39  * Hebojoined
05:25:47  * andris9quit (Remote host closed the connection)
05:33:47  * joshonthewebquit (Quit: Textual IRC Client: http://www.textualapp.com/)
05:35:06  * joshonthewebjoined
05:56:59  * stolsmajoined
06:00:07  * zkirillquit (Quit: zkirill)
06:10:50  * generalissimoquit (Remote host closed the connection)
06:11:34  <kenperkins>indexzero: think we should figure out exactly what compute api falls under the pervue of "multi-provider" so we can have some signature checks or something for them
06:12:10  <kenperkins>indexzero: I'd also like to figure out how to factor the code so the common APIs are in different files than the extension APIs
06:12:28  <kenperkins>so at a glance you can tell if it's something that's specific to your provider, or global
06:12:34  <kenperkins>(i.e. not screwing with signatures)
06:12:39  <indexzero>kenperkins: sounds good, open an issue with a checklist and we'll enumerate it
06:12:45  <indexzero>I know most providers pretty well
06:14:00  * swaagiejoined
06:35:58  * alucardXjoined
06:42:56  <alucardX>morning
06:43:03  <kenperkins>evening
06:43:10  <julianduque>alucardX: morning :)
06:44:32  * admc1quit (Quit: Leaving.)
06:50:37  <alucardX>morning julianduque :)
06:51:10  * andris9joined
06:51:57  * tonistjoined
06:56:05  * tonistquit (Ping timeout: 248 seconds)
07:01:29  * kaspertidemannjoined
07:01:53  * admc1joined
07:05:44  * joshonthewebquit (Quit: Computer has gone to sleep.)
07:06:50  * Nijikoquit (Read error: Connection reset by peer)
07:07:36  * Nijikojoined
07:07:41  * andris9quit (Remote host closed the connection)
07:08:31  * andris9joined
07:10:21  * tonistjoined
07:10:49  * therealkoopaquit (Remote host closed the connection)
07:15:50  * Heboquit
07:19:32  * tonistquit (Ping timeout: 255 seconds)
07:22:33  * tonistjoined
07:26:24  * saqibjoined
07:26:27  <saqib>Hellow
07:27:00  <julianduque>Hello saqib
07:28:06  <saqib>this support given from real technical team of nodejitsu
07:28:32  <julianduque>saqib: yes :)
07:28:42  <julianduque>saqib: How can I help?
07:31:52  * tsausejoined
07:31:58  <saqib>our company developed software with node.js and mongolab and deploy on heroku and we facing lot of issues, and no real time support from them
07:32:38  <saqib>now we have to move on another paas
07:32:38  <tsause>Hi - quick question regarding log files, I have a log file in my app that I dont want to overwrite when I deploy, can I just delete this from my deploy directory, or should I use a .npmignore file with the line "log.txt" in it?
07:33:50  <julianduque>tsause: Nodejitsu storage is temporary, so you always get a new vm on a new deploy, so it's better to persist that kind of logs in a DB, or use a log service like loggly
07:33:59  * Baastrupjoined
07:34:01  <julianduque>saqib: you came to the right place
07:34:15  <julianduque>saqib: have you tried Nodejitsu yet?
07:35:12  <tsause>julianduque: thanks very much will have to look into a DB solution I think.
07:41:31  * `3rdEdenjoined
07:41:43  * tsausequit (Ping timeout: 245 seconds)
07:44:30  * cesconixjoined
07:45:03  <saqib>no
07:47:08  <julianduque>saqib: well, our deploys are a little bit different from heroku, we use our own tool and use npm based deploys
07:47:34  <julianduque>saqib: but if you want to use our Continuous Deployments with Github you can do it :)
07:48:10  <julianduque>saqib: https://www.nodejitsu.com/getting-started/ or https://www.nodejitsu.com/getting-started-with-github/
07:50:20  <julianduque>saqib: you can suscribe for a development sandbox trial and try our service :)
07:51:50  * Dorphernjoined
07:53:43  <saqib>Yesterday we facing problem and now response from heroku and our work is stop due to error. please don't mind i confirmed again this support platform given from technical team of Nodejitsu?
07:54:08  <julianduque>saqib: Yes
07:54:23  <julianduque>saqib: we have to main support channels, this #nodejitsu on IRC and email support
07:54:35  <julianduque>saqib: also, for our business customers we have priority-support :)
07:55:06  <saqib>thanks
07:55:20  <saqib>support 24/7
07:56:28  <julianduque>saqib: only priority, you will find a support team member here from 6am to 8pm EST mon-fri, and beyond that some of us stay here and keep helping :)
07:56:47  * Baastrupquit (Quit: Leaving.)
07:57:03  <swaagie>like now ;)
07:57:24  <julianduque>exactly :D
07:57:51  <julianduque>saqib: but Support is one of our best features :D
07:57:55  * sportoquit (Quit: Textual IRC Client: www.textualapp.com)
07:58:19  * aykutyamanjoined
07:58:51  <saqib>give me any short manual for deploy my complete application on Nodejitsu
07:59:20  <aykutyaman>hello, how can I detect drone usage stats?
08:00:11  <julianduque>aykutyaman: you need to use a third party service like Nodefly (by now...)
08:00:35  <julianduque>saqib: sure, http://nodejitsu.com/getting-started is the first thing you need :)
08:00:48  <julianduque>saqib: more advanced docz https://www.nodejitsu.com/documentation/jitsu/
08:00:51  <aykutyaman>julianduque: ok, thank you
08:00:56  * Dorphernquit (Quit: Dorphern)
08:01:15  <julianduque>aykutyaman: stay tunned :)
08:01:58  <saqib>on heroku we purchase workers and dynos, that's also available on nodejitsu
08:02:21  <julianduque>saqib: we have `drones`
08:02:42  <julianduque>saqib: a `drone` is a VM, with 256mb of RAM (business plans can increase up to 1024mb)
08:03:06  <julianduque>saqib: so you can deploy your app on multiple drones and our load balancers will handle the rest, even SSL :)
08:03:25  <saqib>drone in place of dynos
08:03:30  <saqib>and workers?
08:03:31  <julianduque>saqib: exactly
08:03:34  * rudasnjoined
08:03:54  <julianduque>saqib: you can use drones as workers too, just deploy a dummy http server and then do the background stuff
08:04:15  <saqib>ok.
08:05:08  <julianduque>saqib: and for mongolab, be sure to select the Joyent DC and you will be good :)
08:05:15  <saqib>and mongodb as addons or i can access from direct url db connection
08:05:30  <julianduque>saqib: you can access from direct url :)
08:05:50  <julianduque>saqib: we only support `free tier` on our addons
08:06:21  * aykutyamanpart
08:06:57  <saqib>Silly question but just for confirmation
08:07:03  <saqib>1) Minimum or no change in application
08:07:10  <saqib>2) 24 X 7 technical support with near 100% up time (Automatic Switching) . Even if primary, secondary or tertiary servers have to be rented.
08:07:38  <julianduque>Can you be more specific with 1 ?
08:07:53  <julianduque>2 you will be good with a Business Plan
08:09:09  <saqib>we also use heroku business plan but not satisfaction :(
08:09:28  * alxjoined
08:09:35  * alxquit (Remote host closed the connection)
08:09:54  <julianduque>saqib: give Nodejitsu a try :)
08:10:17  <saqib>sorry no satisfaction
08:11:17  <saqib>we are searching and also we deploy our application on other paas for check the issues.
08:11:20  <julianduque>saqib: If you want you can contact sales@nodejitsu.com :)
08:12:22  * V1joined
08:12:40  <saqib>first i deploy my application and check then contact sales@....
08:12:58  <saqib>tell me about your self
08:13:35  <julianduque>saqib: what do you want to know? I'm from Medellin, Colombia and I'm a happy developer :)
08:13:47  <saqib>from
08:13:53  <saqib>company
08:14:05  <julianduque>Nodejitsu
08:14:09  <julianduque>saqib: https://www.nodejitsu.com/company/#julianduque
08:16:04  <saqib>detail for 1 question ?
08:17:13  <julianduque>saqib: Yes, what do you mean by Minimun or No change?
08:19:37  * LinusUquit (Ping timeout: 245 seconds)
08:20:33  * V1quit (Ping timeout: 256 seconds)
08:21:56  <saqib>in application
08:22:09  <saqib>i mean application we developed
08:22:41  <julianduque>saqib: Minimum changes, mainly in package.json, but you can give it a try and see if it works with no changes
08:24:30  <saqib>we developed node.js application and deploy on heroku use addons which is mongolab rabbit mq and also redis cloud.
08:26:54  * andris9quit (Remote host closed the connection)
08:27:37  <saqib>u have also addons just like heroku or we have to use other addons.
08:27:42  * andris9joined
08:27:56  <saqib>julian r u there ?
08:28:36  <julianduque>saqib: you need to use other addons, like cloudamqp for Rabbit MQ and Iris Redis or Redistogo or Openredis for the redis part
08:28:46  <julianduque>saqib: you can easily create redis instances with `jitsu` cli
08:29:13  <julianduque>saqib: but they are free tier ones
08:29:42  <saqib>free tier ones?
08:29:56  <julianduque>saqib: yes, free plans
08:30:14  <saqib>okay thanks
08:30:25  <julianduque>saqib: well, via Nodejitsu Addons, https://www.nodejitsu.com/paas/addons/
08:30:31  * groodtjoined
08:30:32  <saqib>one thing more
08:31:01  <groodt>Hi. I've got a question about continuous deployment of a private repo.
08:31:17  <groodt>Anybody able to help?
08:31:54  <julianduque>groodt: what do you need?
08:32:13  * Baastrupjoined
08:33:14  * Baastrupquit (Client Quit)
08:34:12  <jesusabdullah>mmalecki[zzz]: ping me when you're up I have questions about cradle
08:34:20  <jesusabdullah>mmalecki[zzz]: don't ask me why I'm using cradle
08:35:04  <groodt>I've got it setup, but I get this error: "non_fatal_errors": { "nodejitsu": { "description": "Request failed", "error": "deploy:nodejitsu:cant_create_app", "name": "Error", "nodejitsu": { "err": { "appname": false, "checked": true, "domain": false, "message": "App name / subdomain
08:35:16  <groodt>although, that is under non_fatal.
08:36:01  <groodt>ah, maybe this is the real error:
08:36:03  <groodt> "err": { "description": "Unspecified error", "error": "deploy:nodejitsu:start_app", "name": "Error", "nodejitsu": { "err": { "message": "haibu Error (500): Internal Server Error", "result": { "error": { "blame": { "message": "Package.json start script declared but not found",
08:36:28  <jesusabdullah>groodt: suggestion: use gists instead of copypasta into the channel
08:37:02  <jesusabdullah>groodt: suggestion: does your package.json script have a scripts:start field and is it correct? Does it point to a javascript file?
08:37:16  <groodt>indeed. Good idea. I'll stick the whole error up in a gist.
08:37:55  * meso_joined
08:38:28  <groodt>so, I've got a start script. And it seems correct to me.
08:38:36  <groodt>The app deploys fine through jitsu deploy
08:39:10  * andris9quit (Remote host closed the connection)
08:40:00  * thealphanerd_joined
08:40:03  <groodt>ah, actually the start script is app.js
08:40:10  <groodt>but the code is coffeescript.
08:40:25  <groodt>how is it then working at all using jitsu deploy I wonder?
08:40:59  * julianduquequit (Quit: leaving)
08:41:41  <jesusabdullah>sounds like you have something to sort out
08:41:56  <jesusabdullah>I believe start scripts can be .coffee files but it's probably better to compile to javascript before deploy
08:41:57  * hourback1joined
08:42:16  <ljharb>s/probably/always :-p
08:42:44  * sunil_joined
08:42:57  <sunil_>ciao a tutti
08:43:20  <saqib>julianduque - Thanks
08:43:27  * saqibquit (Quit: Page closed)
08:43:42  * sunil_quit (Client Quit)
08:45:19  * alx__joined
08:46:18  * swaagiequit (*.net *.split)
08:46:18  * thealphanerdquit (*.net *.split)
08:46:18  * mesoquit (*.net *.split)
08:46:18  * hourbackquit (*.net *.split)
08:46:19  * thealphanerd_changed nick to thealphanerd
08:47:21  * Baastrupjoined
08:49:05  <groodt>ok, I've compiled to js and am trying again.
08:49:16  <groodt>still curious how it was working at all using jitsu deploy.
08:51:04  * swaagiejoined
08:51:21  * saqibjoined
08:52:19  <saqib>hello again Julian Duque
08:52:27  <saqib>u there
08:53:14  * toonketelsjoined
08:54:45  <saqib>hellooooooooooooooooooo.
08:55:07  * Nijiko_joined
08:56:50  <swaagie>saqib, he seems to be offline atm, my IRC connection also got reset
08:57:07  <saqib>ok
08:57:10  <swaagie>anyways ask away, I followed your original conversation with Julian
08:57:27  <saqib>okay
08:57:49  * wookiehangover_joined
08:58:26  <saqib>on heroku we get timeout response error
08:58:47  <saqib>can we change timeout response
08:59:03  * Nijikoquit (*.net *.split)
08:59:04  * indexzeroquit (*.net *.split)
08:59:05  * wookiehangoverquit (*.net *.split)
08:59:05  * wookiehangover_changed nick to wookiehangover
08:59:06  * Nijiko_changed nick to Nijiko
08:59:08  <saqib>or any control panel for this kind of option
09:00:52  <swaagie>saqib, I'm not really familiar with heroku, are you referring to https://devcenter.heroku.com/articles/error-codes#h12-request-timeout?
09:01:03  * 16WAAVUC6joined
09:01:03  * indexzerojoined
09:01:03  * 16WAAUR22joined
09:01:21  * 16WAAUR22quit (Max SendQ exceeded)
09:01:55  * 16WAAVUC6quit (Ping timeout: 246 seconds)
09:03:21  <saqib>please also clear that if i submit request for data to application server or web server then request get data from mongolab if response is delay
09:03:46  <saqib>the timeout error occuers from webapplication or database
09:05:45  <saqib>on nodejitsu timeout response
09:05:57  <saqib>?
09:06:16  <swaagie>saqib, are you referring to the request-timeout of heroku or an actual timeout occuring now that you deployed your application?
09:07:31  * alx__quit (Read error: Connection reset by peer)
09:08:28  <swaagie>saqib, just to know where you guys are in the process, have you signed up to nodejitsu and deployed your application?
09:08:59  * alx__joined
09:09:15  <saqib>i will deploy my application on nodejitsu
09:10:08  <`3rdEden>saqib: we don't impose any timeouts
09:10:12  <swaagie>ok,as for the timeout, we do not have any interface or option to set it
09:10:24  <`3rdEden>you should handle those timeouts inside of your application
09:10:25  * toonketelsquit (Remote host closed the connection)
09:10:34  <saqib>okay
09:10:58  * mikljoined
09:11:10  <swaagie>saqib, is your apps computation so heavy that it will hit those timeouts? e.g. 30secs or greater?
09:12:01  * rcombsquit (Read error: Connection reset by peer)
09:12:15  <saqib>ok you don't impose any timeouts but if response is delay from webserver or database what i get an error
09:13:09  <`3rdEden>saqib: you can handle that at your application level
09:13:10  <swaagie>saqib, an error in the application or an e-mail warning you?
09:13:13  * tonist_joined
09:14:02  <`3rdEden>It's not something we should handle for you. If your database call takes to long, just abort it and return a response to your users.
09:14:03  * Nijiko_joined
09:14:15  * z0w0joined
09:14:47  * itzmjauz1joined
09:15:20  * RushPL_joined
09:16:08  * groodtquit (Quit: Page closed)
09:17:44  <saqib>application will stop or its remain running state?
09:17:47  * toonketelsjoined
09:18:28  * oroce1joined
09:20:39  * miklquit (Ping timeout: 268 seconds)
09:20:52  * kaspertidemannquit (Quit: kaspertidemann)
09:21:23  * JakeVjoined
09:21:25  <saqib>application will stop or its remain running state?
09:21:28  <saqib>application will stop or its remain running state?
09:21:46  * tonistquit (Read error: Connection reset by peer)
09:21:46  * Nijikoquit (Ping timeout: 264 seconds)
09:21:46  * Raynosquit (Ping timeout: 264 seconds)
09:21:47  * RushPLquit (Ping timeout: 264 seconds)
09:21:48  * itzmjauzquit (Ping timeout: 264 seconds)
09:21:48  * orocequit (Ping timeout: 264 seconds)
09:21:48  * tonist_changed nick to tonist
09:22:03  * Nijiko_changed nick to Nijiko
09:22:12  <swaagie>saqib, we have a service that will keep an application up and running for you, even after an occasional error occurs
09:23:01  <swaagie>saqib, if the application stays in an error state/crash loop you will get a notification e-mail
09:23:11  <saqib>can you give me a like of error codes
09:23:17  <saqib>sorry link
09:24:29  <swaagie>we have no special error codes other than default http error codes, errors inside the application would normally just be thrown JS errors
09:24:47  <saqib>ok
09:27:01  * YoYquit (Ping timeout: 248 seconds)
09:27:06  * mokesjoined
09:28:05  * ebrightjoined
09:28:51  * YoYjoined
09:30:31  * admc1quit (Quit: Leaving.)
09:31:54  * toonketelsquit (Remote host closed the connection)
09:37:08  * toonketelsjoined
09:38:35  * alx__quit (Read error: Connection reset by peer)
09:38:36  * alx___joined
09:44:39  * julianduquejoined
09:47:22  * z0w0quit (Quit: Leaving.)
09:47:33  * z0w0joined
09:48:30  * kaspertidemannjoined
09:49:18  * mesojoined
09:49:45  * meso_quit (Read error: Connection reset by peer)
09:56:29  * Baastrupquit (Quit: Leaving.)
09:56:57  * Baastrupjoined
09:57:49  * netj_quit (Read error: Connection reset by peer)
09:58:01  * netjjoined
10:00:40  * Baastrupquit (Client Quit)
10:00:51  * admc1joined
10:09:55  * admc1quit (Ping timeout: 256 seconds)
10:11:24  <mokes>hi - anyone here?
10:12:37  <Nexxy>not a soul
10:19:48  <swaagie>mokes, Nexxy not true! how can I help you mokes?
10:20:24  <mokes>hi - I'm wondering why "jitsu logs" doesn't give me updated, real time logs....
10:21:18  <swaagie>mokes, the logs tored/processed @loggly, there is a slight delay between our services
10:21:25  <swaagie>are stored*
10:21:42  <`3rdEden>And we are working on improving our logging
10:21:46  <mokes>any way to get them faster?
10:22:12  * Dorphernjoined
10:22:14  <`3rdEden>nop
10:22:32  <mokes>my latest logs are from over an hour ago... kinda hard to debug like this
10:25:12  <mokes>and as long as I'm bitching..... (pardon me of course) - I'm repeating ny plea for more Redis vendors
10:25:48  <mokes>I can recommend Redis Cloud - have had a good experience with them so far, but they're not on Joyent yet
10:26:21  <mokes>I asked them - they said it's in the plans, would be good if you guys can somehow help this process
10:27:11  * thealphanerdquit (Quit: thealphanerd)
10:27:51  <swaagie>mokes, your using the cli I assume? logs from -1hour seem a bit harsh, haven't seen it take that long before
10:28:01  <mokes>yup, cli
10:28:27  <swaagie>actually our homepage logs are -1hour as well
10:28:28  <swaagie>:/
10:29:01  <mokes>yup - it says on my console 12:01:33 GMT+3
10:29:16  <mokes>and my local time is 1:29 GMT+3...
10:29:20  <mokes>:(
10:29:27  <swaagie>05/10 11:12:45 GMT+0200 here
10:29:53  <swaagie>so thats atleast 1.15-1.30h
10:30:01  <mokes>yikes
10:30:07  * toonketelsquit (Remote host closed the connection)
10:30:31  <mokes>so when will the logging be taken care of?
10:30:42  * therealkoopajoined
10:30:53  <swaagie>http://loggly.com/status/ seems good though
10:31:12  <mokes>I have to say this is not the first time I've seen this
10:31:13  <julianduque>mokes: we are using loggly by now, but we will be switching to our log strategy soon
10:31:24  <mokes>k - tnx
10:31:32  <swaagie>mokes, haven't got an eta for you concerning that strategy though
10:31:38  <julianduque>mokes: Yes, thats one of the reasons we are changing :)
10:31:43  * toonketelsjoined
10:32:07  <mokes>3rdEden, if you're still here.... unrelated to Nodejitsu... but I believe you're involved with Socket.io?
10:32:07  * toonketelsquit (Remote host closed the connection)
10:32:58  <`3rdEden>mokes: yes, i've done some socket.io stuff
10:33:43  <mokes>so can you share some info on 1.0 release date? Guillermo said "in a few weeks" over a month ago
10:34:13  <mokes>Thinking ahead to my scaling strategy..... :)
10:34:46  <`3rdEden>mokes: he's been saying a few weeks for more then 5 months now
10:34:58  * tonistquit (Quit: tonist)
10:35:00  <`3rdEden>he says that at every major conference XD
10:35:07  <mokes>you're being generous..... lol
10:35:15  * Baastrupjoined
10:35:17  <`3rdEden>I really have no clue, as it's not up to me :p
10:35:35  * Baastrupquit (Client Quit)
10:35:40  <`3rdEden>While I do have GOD MODE access over all the repo's I'm not in a position to release it yet
10:35:47  <mokes>ok - thought u were on the "inside" ;-)
10:35:49  <`3rdEden>but I can say that it's still being worked on
10:36:25  <`3rdEden>I'm on the inside, but that doesn't mean I can just do what ever I want without discussing it first ;)
10:36:33  * toonketelsjoined
10:37:21  <mokes>To be honest - socket.io is a wonderful project - but for a project with so many followers and users, it gets precious little public attention from its maintainers
10:37:44  <mokes>makes me nervous regarding relying on it
10:39:00  <`3rdEden>mokes: understandable but it's a side project and ideally it should be backed by some sort of funding so it can be worked on consistently because in the end, we're all developers with regular day jobs and there needs to be some food on the table ;)
10:39:48  <mokes>well, ahem..... seeing as Nodejitsu stands to be the primary platform for socket.io projects..... ergo.....
10:39:49  <mokes>;-)
10:40:04  <mokes>hint hint wink wink
10:40:08  <`3rdEden>mokes: ;)
10:40:11  <mokes>cough cough
10:40:48  <`3rdEden>that's why i'm helping you for free without charging you $90 per hour as a consultant ;)
10:40:56  <julianduque>touche
10:41:35  <mokes>much appreciated :) But it works both ways, and I'm also interested in your success
10:41:48  <mokes>So for example - socket.io bug reports, etc
10:42:14  <mokes>and would be willing to contribute, etc - but in the case of socket.io there is no one to even talk to about it
10:43:35  <`3rdEden>I haven't touched any bugs reports because of nearing release of socket.io 1.0
10:43:51  <`3rdEden>which is a complete refactor and we decided to focus our energy on that
10:44:12  <`3rdEden>the bug base it self has become to weedy to manage
10:44:25  * switzquit (Quit: Leaving...)
10:44:30  <`3rdEden>github isn't the best platform to manage such a large project
10:44:39  <`3rdEden>(issue wise)
10:44:44  <mokes>sorry about the monolog - but stuff like socket.io, websockets, scaling, etc - this is what differentiates you guys from established players like Heroku
10:44:50  <mokes>monologue
10:45:23  <mokes>so please - any pull you have on advancing this..... it's key to all of us
10:45:52  <`3rdEden>mokes: I know, I know but my hands are as tied as yours
10:46:04  <`3rdEden>we're both waiting for socket.io 1.0 to come out
10:46:26  <`3rdEden>and I can say it's being worked on, there's even a team of MIT students working on socket.io 1.0
10:46:28  <`3rdEden>to get it ready
10:46:40  <mokes>ok - tnx. ranted enough this morning :) sorry about the headache
10:47:01  <`3rdEden>as much as I hate to say this, i'm used to that
10:47:12  <mokes>ouch
10:49:40  <mokes>one more q.... (i think it may be the last one for now):
10:50:05  <mokes>does nodejitsu do any cacheing before the requests hit our drones?
10:51:12  <mokes>and related to this... it would be awesome if you had a "recipe" for recommended node/express cache setups that would play nice with your infrastructure
10:52:33  <mokes>talking about static file caching of course...
10:57:54  * mmalecki[zzz]changed nick to mmalecki
10:58:16  <mmalecki>jesusabdullah: ping
11:01:24  * admc1joined
11:03:33  * Baastrupjoined
11:06:02  * admc1quit (Ping timeout: 252 seconds)
11:12:48  * indexzeroquit (Quit: indexzero)
11:14:10  * mokesquit (Remote host closed the connection)
11:15:25  * mokesjoined
11:20:37  * papachanjoined
11:21:28  <`3rdEden>mokes: we don't do any caching of requests
11:21:57  <`3rdEden>for our own websites we've developed versions as caching solution
11:22:09  <`3rdEden>http://blog.nodejitsu.com/content-delivery-network-in-node-js
11:22:18  <`3rdEden>https://github.com/3rd-Eden/versions
11:32:52  * mokesquit (Remote host closed the connection)
11:39:44  * c4milojoined
11:42:36  * alex_____joined
11:43:37  <alex_____>Is it possible to have my app hosted in Holland instead of the US?
11:46:01  * tonistjoined
11:50:31  <`3rdEden>alex_____: you can select datacenter when you are running our business plans
11:50:59  <`3rdEden>https://www.nodejitsu.com/paas/datacenters/ here are our datacenter locations, including Amsterdam :)
11:51:10  <alex_____>Thank you `3rdEden!
11:51:40  * alex_____part
11:51:42  * mokesjoined
11:53:12  * alucardXquit (Quit: leaving)
11:53:51  <mokes>@3rdEden - tnx for the info
12:01:58  * admc1joined
12:06:42  * admc1quit (Ping timeout: 264 seconds)
12:13:48  * saqibquit (Ping timeout: 245 seconds)
12:20:00  * Sly__joined
12:20:12  * Sly__changed nick to Sly
12:26:56  * fusiongrokkerjoined
12:29:49  * mokesquit (Remote host closed the connection)
12:31:43  * bobbybuilderquit (Ping timeout: 245 seconds)
12:32:01  * thealanwattsriotjoined
12:32:47  * admc1joined
12:37:25  * admc1quit (Ping timeout: 276 seconds)
12:39:16  * c4miloquit (Remote host closed the connection)
12:40:42  * sirkitreejoined
12:45:15  * c4milojoined
12:49:12  * c4miloquit (Remote host closed the connection)
12:56:11  * akashajoined
13:03:37  * admc1joined
13:08:29  * admc1quit (Ping timeout: 256 seconds)
13:10:19  * jgablejoined
13:14:28  * mdedetrichjoined
13:22:13  * mdedetrichquit (Remote host closed the connection)
13:23:14  * mdedetrichjoined
13:23:22  * thealanwattsriotquit (Quit: Textual IRC Client: www.textualapp.com)
13:28:59  * mokesjoined
13:29:35  * mdedetrichquit (Remote host closed the connection)
13:30:35  * mdedetrichjoined
13:31:24  * thealanwattsriotjoined
13:34:29  * admc1joined
13:37:23  * mokesquit (Ping timeout: 256 seconds)
13:37:53  * mdedetrichquit (Remote host closed the connection)
13:38:38  * c4milojoined
13:39:06  * admc1quit (Ping timeout: 264 seconds)
13:39:19  * mdedetrichjoined
13:44:17  * mdedetrichquit (Remote host closed the connection)
13:45:29  * Hounddogjoined
13:45:42  * mdedetrichjoined
13:48:40  * kevino80joined
13:52:37  * defunctzombie_zzchanged nick to defunctzombie
13:53:16  * mdedetrichquit (Remote host closed the connection)
13:54:43  * mdedetrichjoined
13:54:48  * mokesjoined
13:57:20  * mdedetrichquit (Client Quit)
13:59:24  * mokesquit (Remote host closed the connection)
14:03:18  * stolsmaquit (Ping timeout: 272 seconds)
14:05:16  * admc1joined
14:07:24  * mokesjoined
14:09:02  * akashaquit (Quit: T�vozom)
14:09:25  * admc1quit (Read error: Operation timed out)
14:11:44  * sreeixquit (Quit: sreeix)
14:15:58  * jetiennequit (Quit: jetienne)
14:17:52  * arush1joined
14:19:25  <arush1>hey guys looks like our SSL is broken again but only for some visitors
14:19:44  <arush1>can you please check, last time the cert got corrupted somehow
14:20:58  * tgriesserjoined
14:23:35  <mokes>hi, just a quick check to make sure I'm not missing something: is there any way to upload individual files, i.e. html, js, css, etc or do I need to do "jitsu deploy" every time? i.e. does my server need to restart whenever I update a file resource?
14:24:18  * mdedetrichjoined
14:25:36  <mmalecki>mokes: you have to do full deploy whole time
14:25:43  <mmalecki>mokes: also, it's zero downtime
14:25:47  <mmalecki>so no harm done
14:25:59  <mmalecki>arush1: yo. username and appname? which domain is it on?
14:26:20  <mokes>how is it zero downtime? my app needs to restart
14:27:00  <mokes>any plans on enabling public file uploads?
14:27:10  <arush1>brandid/shinobi
14:27:13  <arush1>no sorry
14:27:16  <arush1>brandid/escobar
14:28:20  <arush1>mokes, the app restarts but visitors can't tell = zero downtime
14:30:01  <mokes>are all outstanding user requests completed before the app reboot?
14:30:08  * tgriesserquit (Remote host closed the connection)
14:30:19  <mokes>if not.... imagine you're in a series of DB writes.... ouch
14:30:42  <mmalecki>arush1: https://www.getbrandid.com/#/ - looks fine from here. do you happen to have more details? checking all other balancers now
14:35:09  <kenperkins>o/
14:36:08  * admc1joined
14:36:47  * tgriesserjoined
14:40:32  * admc1quit (Ping timeout: 252 seconds)
14:41:03  <mmalecki>arush1: wait
14:41:12  <mmalecki>arush1: is your site operational?
14:41:18  <mmalecki>like, can I get someone to shop for me?
14:41:18  * jcrugzzquit (Ping timeout: 272 seconds)
14:43:36  <mmalecki>arush1: found one balancer failing, investigating more
14:43:57  * kaspertidemannquit (Quit: kaspertidemann)
14:45:48  * mokesquit (Remote host closed the connection)
14:46:04  * papachanquit (Quit: Saliendo)
14:47:13  * rosskjoined
14:49:13  * z0w0quit (Quit: Leaving.)
14:51:06  * leichtgewichtquit (Remote host closed the connection)
14:51:11  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
14:51:38  * mokesjoined
14:52:26  * leichtgewichtjoined
14:55:41  * Hounddogquit (Read error: Connection reset by peer)
14:57:19  * thealanwattsriotjoined
14:57:50  * anoemijoined
14:58:01  * switzjoined
14:58:33  * tonistquit (Quit: tonist)
14:59:37  * mokesquit (Remote host closed the connection)
15:00:08  * Hounddogjoined
15:03:48  * zkirilljoined
15:06:32  * admc1joined
15:08:29  * `3rdEdenquit (Remote host closed the connection)
15:10:55  * admc1quit (Ping timeout: 256 seconds)
15:16:41  * sreeixjoined
15:17:08  * cronopiojoined
15:20:31  * mdedetrichquit (Quit: Computer has gone to sleep.)
15:30:52  * defunctzombiechanged nick to defunctzombie_zz
15:33:08  * jgablequit (Quit: Computer has gone to sleep.)
15:37:24  * admc1joined
15:40:58  * jgablejoined
15:42:08  * admc1quit (Ping timeout: 252 seconds)
15:43:03  * generali_joined
15:44:56  * zkirillquit (Quit: zkirill)
15:44:57  * mokesjoined
15:47:37  * jcrugzzjoined
15:51:46  * jcrugzzquit (Read error: Operation timed out)
15:56:51  * mokesquit (Remote host closed the connection)
15:58:48  * mokesjoined
16:08:12  * admc1joined
16:08:14  * jcrugzzjoined
16:13:13  * admc1quit (Ping timeout: 276 seconds)
16:15:50  * TooTallNatejoined
16:21:36  * mokesquit (Remote host closed the connection)
16:21:50  * jgablequit (Quit: Computer has gone to sleep.)
16:25:18  * jamundjoined
16:30:46  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
16:31:30  * therealkoopaquit (Ping timeout: 272 seconds)
16:33:53  * ebrightquit (Ping timeout: 256 seconds)
16:34:41  * jgablejoined
16:36:36  * mokesjoined
16:37:14  * mokesquit (Remote host closed the connection)
16:39:03  * admc1joined
16:39:13  * erichoceanjoined
16:39:38  * sw1tchjoined
16:40:02  * standoo1joined
16:42:01  * alx___changed nick to alx__
16:43:21  * TooTallNatequit (Quit: Computer has gone to sleep.)
16:43:43  * admc1quit (Ping timeout: 264 seconds)
16:44:05  * standooquit (Ping timeout: 252 seconds)
16:54:33  <kenperkins>mmalecki still awake
16:55:49  <mmalecki>kenperkins: nah, went to sleep
16:56:10  <kenperkins>:(
16:56:22  <mmalecki>kenperkins: I mean, how long can I be awake?
16:56:29  <kenperkins>days, apparently
16:56:31  <mmalecki>I gave myself solid 6 hours of sleep this night
16:56:42  <jcrugzz>:3b
16:56:48  <jcrugzz>damnit
16:56:48  <jcrugzz>>.<
17:00:43  * TooTallNatejoined
17:01:18  * anoemiquit (Ping timeout: 264 seconds)
17:02:16  * mokesjoined
17:02:46  * oroce1quit (Quit: Leaving.)
17:04:52  * anoemijoined
17:09:57  * admc1joined
17:11:30  * thealanwattsriotjoined
17:14:58  * admc1quit (Ping timeout: 276 seconds)
17:21:02  * admc1joined
17:26:03  * alx__quit (Remote host closed the connection)
17:29:24  * anoemi_joined
17:29:45  * jamundquit (Quit: jamund)
17:30:43  * jxsonjoined
17:30:45  * joshonthewebjoined
17:32:10  * anoemi_quit (Client Quit)
17:32:13  * anoemiquit (Ping timeout: 245 seconds)
17:33:12  * jamundjoined
17:33:33  * backinnamjoined
17:33:49  * backinnamquit (Client Quit)
17:33:56  * sw1tchquit (Quit: sw1tch)
17:35:19  * joshonthewebquit (Ping timeout: 264 seconds)
17:37:01  * towskijoined
17:38:34  <mokes>hi - question I asked earlier which was perhaps missed:
17:39:04  <mokes>any way to do a graceful app shutdown when redeploying an app?
17:39:50  <mokes>i.e. notification of pending shutdown to give us a chance to cleanup and deny new requests?
17:40:09  <Sly>mokes: process.on('exit', ...), iirc
17:40:34  <mokes>but isn't it a bit late at that point?
17:40:51  * sreeixquit (Quit: sreeix)
17:40:59  <mmalecki>mokes: new requests are rerouted to new instance
17:41:20  <mokes>and current ones? will they have a chance to complete?
17:41:50  <mmalecki>nope, we call stop as soon as new app is up. good call tho.
17:42:36  <mmalecki>I'll turn that into an issue
17:43:59  <mokes>ok, thanks. in my app - would be a key feature. imagine i'm doing multiple mongodb updates per a single client request - don't want that to die in the middle just because I deployed because some update on a static file, etc
17:44:00  * joshonthewebjoined
17:49:53  * swaagiequit (Quit: Leaving)
17:51:19  * JakeVchanged nick to Raynos
17:55:00  * sw1tchjoined
18:01:24  * mokesquit (Remote host closed the connection)
18:03:34  * thealphanerdjoined
18:06:47  * zkirilljoined
18:07:47  * jetiennejoined
18:12:12  * everettjoined
18:12:49  <everett>anybody who can help with jitsu deploy - not working?
18:13:07  * sw1tchpart
18:14:34  * AdamMagalukjoined
18:15:07  * travis-cijoined
18:15:07  <travis-ci>[travis-ci] rackspace/pkgcloud#65 (signatureTests - e7e0482 : Ken Perkins): The build passed.
18:15:07  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/commit/e7e0482dfaf8
18:15:07  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7061545
18:15:07  * travis-cipart
18:15:44  <AdamMagaluk>Where is the best place to find help with Nodejitu's haibu project?
18:16:31  <mmalecki>AdamMagaluk: here
18:17:33  <AdamMagaluk>Great: I'm looking for any info/help on deploying haibu across multiple machines and syncing the configurations of drones between the haibu process.
18:17:53  <everett>@mmalecki, i need some help on getting jitsu deploy to work
18:18:16  * Nodejitsu-Githubjoined
18:18:16  * Nodejitsu-Githubpart
18:18:24  <mmalecki>AdamMagaluk: you mean haibu configuration or drone config?
18:18:40  <mmalecki>AdamMagaluk: if it's drone config, I'd go with env variables
18:18:47  <mmalecki>everett: yo. what's up?
18:19:09  <everett>i got this error when I tried jitsu deploy
18:19:12  * travis-cijoined
18:19:12  <travis-ci>[travis-ci] rackspace/pkgcloud#66 (signatureTests - da9a727 : Ken Perkins): The build passed.
18:19:12  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/compare/e7e0482dfaf8...da9a727fbf11
18:19:12  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7061659
18:19:12  * travis-cipart
18:19:38  <everett>nfo: Analyzing application dependencies in WARN package.json eqsoftware@0.0.1 No repository field. WARN package.json eqsoftware@0.0.1 No readme data. info: Checking app availability eqsoftware info: Checking app availability eqsoftware info: Creating app eqsoftware info: Creating app eqsoftware info: Creating snapshot 0.0.1 error: Error creating eqsoftware error: Nodejitsu Error (500): Internal Server Erro
18:20:12  * `3rdEdenjoined
18:20:13  <mmalecki>everett: gist please
18:20:36  <julianduque>everett: what is your username?
18:21:06  <everett>https://gist.github.com/anonymous/5556333
18:21:21  <everett>@julianduque - EverettQuebral
18:21:51  * joshonthewebquit (Quit: Computer has gone to sleep.)
18:22:25  <AdamMagaluk><mmalecki>: Not sure what I need, Is there any way to store the configuration for what apps should be running/installed in some central db like redis or mongo.
18:23:01  <julianduque>everett: I will see what happened to the deploy and I recommend to you to upgrade to latest node (0.8.22 or 0.10.5) for a better experience with jitsu cli <3
18:23:05  <mmalecki>AdamMagaluk: not really, no. you have to build the synchronization layer
18:23:33  * ljharb_workquit (Ping timeout: 248 seconds)
18:23:47  <everett>@julianduque, thanks, will try that
18:24:35  * mokesjoined
18:24:58  <AdamMagaluk>mmalecki: Have you seen this done before?
18:25:40  <mmalecki>AdamMagaluk: well, our master API does that
18:25:52  <mmalecki>but nothing open source, sorry
18:25:54  <julianduque>everett: can you retry again a deploy, it seems that the snapshot wasn't uploaded
18:28:07  <everett>@julianduque, got a different error - https://gist.github.com/anonymous/5556397
18:28:28  <julianduque>everett: something is wrong, let me check
18:32:42  * lwicksjoined
18:35:30  * lwicksquit (Client Quit)
18:36:30  * therealkoopajoined
18:36:49  <julianduque>everett: can you create a gist with your package.json please?
18:40:08  <everett>https://gist.github.com/EverettQuebral/5556469
18:40:18  <julianduque>everett: thats it !
18:40:35  <everett>what did I miss?
18:40:43  <julianduque>everett: 1. You need a start script, in "start" field make sure to add something like "start": "node server.js"
18:40:56  <julianduque>and you need to add dependencies
18:41:07  * NodeJSjoined
18:41:13  * cronopio[phone]joined
18:41:30  <julianduque>everett: check node_modules folder and make sure to install the deps on your package.json, you can do it by running `npm install mydep --save` and it will be added to your package.json
18:42:22  <everett>oic, sorry my bad
18:42:28  <NodeJS>Hello everyone I want to build own senver with delpoing like nodejitsu. Is it something like this in opensource?
18:42:58  <everett>julianduqueL i
18:42:59  <julianduque>NodeJS: well, you have http://github.com/nodejitsu
18:43:18  <everett>julianduqueL i'll try to create a simple app, then try it again. thanks for your help
18:43:28  <NodeJS>Basacly I need to make several snapshoots and rollback if an erro take place
18:43:30  <julianduque>NodeJS: check for haibu*
18:44:05  <NodeJS>julianduque does haibu supports spapshoots?
18:44:53  <NodeJS>sorry snapshoots
18:45:03  <julianduque>NodeJS: haibu is the app server, so you deploy a snapshot (.tgz) and it will run your app
18:45:46  <julianduque>NodeJS: and you can roll your own snapshot creation with rollback stuff
18:46:38  <NodeJS>julianduque: as I\ve seen from documentation: haibu is the open-source node.js project used at Nodejitsu's for spawning and managing several node.js applications on a single server. But I have the single application
18:47:02  <NodeJS>Does it will overhead for me?
18:47:37  * everettquit (Quit: Page closed)
18:47:40  * Baastrupquit (Quit: Leaving.)
18:50:31  <NodeJS>Are there good tutorials for setting up haibu on dedicated server?
18:51:30  <julianduque>NodeJS: no, there isn't, check doc on nodejitsu/haibu
18:52:08  * ljharb_joined
18:53:00  <NodeJS>It's not enough for me. How could I take snapshoots and roll bake if error without haibu?
18:53:40  <julianduque>NodeJS: a snapshot is the result of `npm pack` right?
18:53:40  * tonistjoined
18:54:14  <julianduque>NodeJS: so you need to deploy and start the app to haibu and check for errors, then you take the last working version of your snapshots and deploy that instead
18:54:21  * sreeixjoined
18:54:22  <julianduque>NodeJS: well, you need to figure out and write your logic
18:55:49  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
18:56:40  * leichtgewichtquit (Remote host closed the connection)
18:57:12  * leichtgewichtjoined
18:57:21  * thealanwattsriotjoined
18:57:34  <NodeJS>julianduque>: Can you provide any tutorials?
18:57:59  <julianduque>NodeJS: Sorry, I don't know a tutorial on this
18:58:16  * leichtge_joined
18:58:23  * Slyquit (Ping timeout: 255 seconds)
18:59:28  <mmalecki>my general tip about haibu is to avoid it at large scale
18:59:33  <mmalecki>but it might work for you
18:59:37  * sreeixquit (Ping timeout: 276 seconds)
18:59:37  <julianduque>NodeJS: but it's a great oportunity, experiment with the code and write one yourself :)
19:00:31  * sreeixjoined
19:02:01  * sreeixquit (Client Quit)
19:02:06  * leichtgewichtquit (Ping timeout: 276 seconds)
19:02:23  * Slyjoined
19:02:53  * leichtge_quit (Ping timeout: 252 seconds)
19:03:44  * erichoceanquit (Quit: erichocean)
19:03:52  * joshonthewebjoined
19:07:59  * towskiquit (Read error: Connection reset by peer)
19:08:26  * towskijoined
19:08:46  <AdamMagaluk>mmalecki: Can you elaborate on your tip?
19:09:42  * YoYquit (Ping timeout: 264 seconds)
19:11:00  * thealphanerdquit (Quit: thealphanerd)
19:11:22  * YoYjoined
19:14:08  * eschnoujoined
19:15:42  * admc1quit (Quit: Leaving.)
19:20:21  * rudasnquit (Quit: rudasn)
19:20:28  * NodeJSquit (Ping timeout: 245 seconds)
19:23:48  <AdamMagaluk>Does haibu put any networking component in front of a deployed app?
19:24:05  <nathan7>No.
19:24:36  <nathan7>There's the net plugin in haibu-carapace (which is what haibu launches the apps with) that allows you to hook net.Socket#listen
19:26:52  * `3rdEdenquit (Remote host closed the connection)
19:27:09  * aykutyamanjoined
19:27:31  <AdamMagaluk>nathan7: Great that's what I thought. Thanks
19:27:56  <aykutyaman>hello, I wonder if I can listen on more than one port.
19:28:04  * lpinjoined
19:28:06  <nathan7>aykutyaman: No, not really
19:28:16  <nathan7>aykutyaman: You can attach multiple things to one HTTP server though
19:29:07  * sandfoxjoined
19:30:40  <aykutyaman>nathan7: I have some problems with socket.io. I think the problem is with some firewall and antivirus apps. I didn't understand what you mean with "attach multiple thins"
19:32:12  * anoemijoined
19:32:55  * sreeixjoined
19:32:57  * sreeixquit (Client Quit)
19:34:00  <nathan7>aykutyaman: You can attach socket.io and the rest of your app to one port
19:34:19  <aykutyaman>nathan7: ok thanks
19:35:11  * therealk_joined
19:35:14  <kenperkins>woo hoo, domain sniped :D
19:36:36  <kenperkins>does this work for ya'll
19:36:38  <kenperkins>http://mylifeincode.com/
19:36:51  <julianduque>kenperkins: works for me
19:36:54  <kenperkins>sweet
19:37:18  * therealkoopaquit (Read error: Connection reset by peer)
19:45:42  * jxsonquit (Remote host closed the connection)
19:46:10  * arush1quit (Quit: This computer has gone to sleep)
19:51:38  * Hebojoined
19:57:29  * jamundquit (Quit: jamund)
19:57:31  * straxquit (Ping timeout: 264 seconds)
19:59:08  * jamundjoined
19:59:15  <rossk>nice kenperkins
20:09:03  * themgtjoined
20:10:14  <mokes>@aykutyaman: I've run into firewall issues too with socket.io. What seems to work best is to do socket.io over SSL and then no one will touch you on the way
20:10:26  <mokes>at least that's been my experience...
20:10:53  * lwicksjoined
20:12:03  * tonistquit (Quit: tonist)
20:12:26  <aykutyaman>mokes: I did socket.io over ssl and it's resolved some problems. but for some users problem continues
20:12:58  <mokes>socket.io has all sorts of issues, not all related to firewalls :)
20:13:38  <aykutyaman>mokes: trello runs smoothly, I wonder how they resolved this issue
20:14:01  <mokes>which issue?
20:14:10  <nathan7>Yeah, socket.io will stop sucking at 1.0
20:14:32  <mokes>I have had all sorts of issues - but firewalls, AVs, etc stopped when I started with SSL
20:14:35  <aykutyaman>mokes: connection problem
20:15:07  * cesconixquit (Quit: Computer has gone to sleep.)
20:16:06  <mokes>@nathan7 - assuming 1.0 is released... it's been "almost here" for a year now, maybe longer
20:17:55  * jamundquit (Quit: jamund)
20:18:17  * joshonthewebquit (Quit: Computer has gone to sleep.)
20:19:51  * jxsonjoined
20:21:04  <nathan7>Well, engine.io is here already
20:21:53  * jamundjoined
20:22:09  * lwicksquit (Quit: lwicks)
20:22:14  <mokes>Guillermo said socket.io 1.0 hinges on engine.io 0.6... which is not out yet
20:23:17  <mokes>@aykutyaman: took a look at Trello.... from a quick peek it seems that they totally hacked up an old version of socket.io...
20:24:06  <mokes>it's basically no longer socket.io - just from reading comments in the code
20:25:08  <aykutyaman>mokes: interesting. maybe socket.io have to copy some things from trello :)
20:25:08  <jcrugzz>yea engine.io is your best bet. you just gotta do a little more code yourself for the sugar
20:25:40  <mmalecki>why not ws?
20:25:51  <mokes>if you go that route - why not sock.js?
20:26:05  * jxsonquit (Ping timeout: 256 seconds)
20:26:14  <mokes>ws doesn't work with many clients - e.g. Android browser
20:26:34  <jcrugzz>browsers still too broken
20:26:42  <aykutyaman>mokes: I will consider some other solution
20:26:47  <jcrugzz>(bcause people are all on old shit)
20:26:49  <mokes>not to mention IE prior to 10.....
20:27:22  <mmalecki>mokes: also maybe Pusher, if you're into external solutions
20:27:46  * c4miloquit (Remote host closed the connection)
20:29:38  <mokes>@mmalecki - I can't really justify an external solution with node
20:29:50  <mokes>seems pointless...
20:30:05  <mokes>the app needs to scale in any case, assuming it's any good...
20:30:21  <mokes>even if u go with external comm solution
20:30:44  <mokes>so the only reason to go to Pusher is because of transport code bugs?
20:31:35  * harbhubjoined
20:31:37  * Heboquit
20:31:40  * sirkitreechanged nick to sirkitree|afk
20:31:48  <harbhub>hey fellas
20:32:27  <jcrugzz>o hai
20:32:28  * Hebojoined
20:32:43  * admc1joined
20:33:34  <nathan7>EBROWSERSTOOSHITTY q=
20:33:49  <harbhub>lol nathan and jcrugzz
20:33:56  <harbhub>good to see you guys
20:34:03  <harbhub>whatcha been up to?
20:34:22  <nathan7>..I slept from 6AM to 8PM
20:34:29  <jcrugzz>working on lots of fun things to come
20:34:32  <jcrugzz>and not sleeping
20:34:53  <harbhub>lolz nice and nice
20:34:54  <nathan7>I spent yesterday in a suit. Suits are awesomer than I expected.
20:35:02  <harbhub>why were you suited up?
20:35:15  <nathan7>To surprise another hackerspace member!
20:35:20  <harbhub>haha
20:35:31  <harbhub>crugz whatcha workin on?
20:35:57  * chjjquit (Quit: leaving)
20:36:09  * chjjjoined
20:36:12  <harbhub>hey in the jitsu website
20:36:14  <jcrugzz>the monitoring stuff we will be implementing to give us all the datas
20:36:22  <harbhub>how did you make the GUI with the little triangle thing under the active tab?
20:36:37  <harbhub>oOoOoh data monitoring
20:36:38  * ljharb_changed nick to ljharb_work
20:37:41  <harbhub>oh i checked the source looks like it is an image
20:39:28  <kenperkins>w00t
20:42:00  <rossk>i'm playing with data monitoring too -- I <3 metrics
20:42:10  <rossk>and pretty graphs
20:43:57  <kenperkins>rackspace monitoring?
20:44:19  <jcrugzz>rossk: yess. graphite is pretty cool. I want a node based graphite that uses levelup
20:44:25  <kenperkins>oh graphite
20:44:27  <kenperkins>yes awesome
20:44:37  <jcrugzz>on my to experiment list
20:44:39  <rossk>kenperkins, monitoring our instances running in rax
20:44:46  <rossk>(or aws, or anything else)
20:45:17  <rossk>the monitoring you've got doesn't work with our dynamic system
20:45:43  <rossk>AND we have additional metrics that come from our platform running in the instance that I'd like to track
20:45:47  <yawnt>kenperkins: congrats :)
20:45:59  <kenperkins>congrats, or, perhaps, I'm sorry? :D
20:46:16  <yawnt>definitely the former
20:46:17  <kenperkins>seriously, ty
20:46:23  <harbhub>hey does nodejitsu use rackspace?
20:46:28  <jcrugzz>kenperkins++
20:46:34  <nathan7>harbhub: Nope
20:46:35  <kenperkins>harbhub: pretty sure they hate us: D
20:46:40  <kenperkins>i kid
20:46:41  <jcrugzz>lol
20:46:43  <rossk>:P
20:46:44  <harbhub>you guys have your own servers in a data center?
20:46:47  <nathan7>harbhub: well, for storing snapshots
20:46:57  * c4milojoined
20:46:59  <nathan7>harbhub: we run on Joyent cloud and Telefonica's cloud
20:47:01  <julianduque>we use cloudfiles, harbhub
20:47:10  <harbhub>ok
20:47:12  <nathan7>harbhub: Telefonica is just London and Madrid
20:49:24  * jxsonjoined
20:51:26  * jakejoined
20:51:49  * jakechanged nick to Guest14774
20:52:57  <harbhub>who made the GUI for the jitsu website?
20:53:05  <Guest14774>hey guys, quick question if you have a sec.. this is my first time using jitsu, and I'm getting an error on deploy: Error 500, No matching versions found
20:53:32  <Guest14774>Is this a version error for the node engine, or one of my dependencies?
20:53:35  <jcrugzz>Guest14774: we dont currently support 0.10.x. change your node engine in the package.json to 0.8.x
20:53:55  <jcrugzz>but 0.10.x support is in the works :)
20:53:57  <Guest14774>aaahhh ok
20:54:02  <Guest14774>thanks much :)
20:54:08  <jcrugzz>np
20:54:22  <Guest14774>is there a rough time frame for 0.10?
20:55:38  * Slyquit (Ping timeout: 252 seconds)
20:55:47  * Slyjoined
20:55:58  * admc2joined
20:56:06  <jcrugzz>i dont have an exact date for you unfortunately :/. We have been hard at work on many different pieces to improve our cloud :)
20:57:09  * admc3joined
20:57:37  <Guest14774>sounds great, thanks again
20:58:03  * Sly__joined
20:58:10  * admc1quit (Ping timeout: 246 seconds)
20:58:14  <jcrugzz>no problem!
20:58:43  * cesconixjoined
21:01:10  * admc2quit (Ping timeout: 276 seconds)
21:01:19  * jahajoined
21:01:20  * alx__joined
21:01:49  * Slyquit (Ping timeout: 276 seconds)
21:02:17  * Sly__quit (Remote host closed the connection)
21:03:15  <nathan7>harbhub: `3rd-Eden and Swaagie are our frontend dudes
21:03:33  <harbhub>ok
21:06:15  * Guest14774quit (Quit: Page closed)
21:10:59  * therealk_quit (Remote host closed the connection)
21:15:35  * eschnouquit (Ping timeout: 256 seconds)
21:17:32  * fusiongrokkerquit (Quit: fusiongrokker)
21:20:18  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:22:51  * thealphanerdjoined
21:26:28  * joshonthewebjoined
21:27:12  * sirkitree|afkchanged nick to sirkitree
21:30:36  * straxjoined
21:32:54  * cesconixquit (Ping timeout: 276 seconds)
21:36:07  * kevino80quit (Remote host closed the connection)
21:39:00  * lpinquit (Quit: Leaving)
21:41:36  * kaspertidemannjoined
21:42:12  * alx__quit (Remote host closed the connection)
21:42:16  * jgablequit (Quit: Computer has gone to sleep.)
21:43:19  <rossk>kenperkins, glad to see you're a contrib now
21:43:35  <rossk>kenperkins++ again
21:43:48  <kenperkins>:)
21:44:06  <kenperkins>just means now i need code reviews more than ever
21:44:34  <rossk>haha
21:44:45  <kenperkins>for example: https://github.com/nodejitsu/pkgcloud/pull/126
21:47:10  * alx__joined
21:48:08  <rossk>mhmm
21:50:49  * alx__quit (Read error: Connection reset by peer)
21:53:23  * alx__joined
21:58:21  * alx__quit (Remote host closed the connection)
22:00:08  * cesconixjoined
22:02:36  * anoemiquit (Quit: anoemi)
22:05:21  * joshonthewebquit (Quit: Computer has gone to sleep.)
22:05:24  * ljharb_workquit (Ping timeout: 276 seconds)
22:06:19  * joshonthewebjoined
22:08:57  * alx__joined
22:12:40  * ljharb_joined
22:14:19  * ljharb_quit (Remote host closed the connection)
22:14:42  * ljharb_joined
22:16:14  * ljharb_changed nick to ljharb_work
22:18:37  * Slyjoined
22:19:09  * Slyquit (Remote host closed the connection)
22:19:45  * zkirillquit (Quit: zkirill)
22:19:56  * anoemijoined
22:21:51  * mokesquit (Remote host closed the connection)
22:31:04  * mokesjoined
22:35:04  * tgriesserquit (Remote host closed the connection)
22:36:06  * tgriesserjoined
22:43:48  * tgriesserquit (Remote host closed the connection)
22:46:24  * aykutyamanpart
22:58:53  * toonketelsquit (Remote host closed the connection)
22:59:01  * switzquit (Quit: Leaving...)
23:06:02  * chrisdotcodequit (Remote host closed the connection)
23:10:48  * mokesquit (Remote host closed the connection)
23:14:45  * arushjoined
23:15:43  * Dorphernquit (Quit: Dorphern)
23:16:35  * julianduquequit (Quit: leaving)
23:17:02  * julianduquejoined
23:17:51  * jxsonquit (Remote host closed the connection)
23:18:24  * jxsonjoined
23:18:44  * RushPL_quit (Quit: No Ping reply in 180 seconds.)
23:19:16  * sirkitreechanged nick to sirkitree|afk
23:19:18  * RushPLjoined
23:20:50  * c4miloquit (Remote host closed the connection)
23:23:31  * jxsonquit (Ping timeout: 276 seconds)
23:28:45  * jahaquit (Quit: Leaving.)
23:29:16  * admc3quit (Quit: Leaving.)
23:32:54  * arushquit (Quit: This computer has gone to sleep)
23:36:58  * travis-cijoined
23:36:58  <travis-ci>[travis-ci] rackspace/pkgcloud#67 (raxIdentity - 647c16d : Ken Perkins): The build passed.
23:36:58  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/compare/9feeb80866a1...647c16df0488
23:36:58  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7069787
23:36:58  * travis-cipart
23:38:00  * kaspertidemannquit (Quit: kaspertidemann)
23:41:19  * mokesjoined
23:42:15  * thepumpkinquit (Remote host closed the connection)
23:42:49  * thepumpkinjoined
23:45:28  * mokesquit (Ping timeout: 246 seconds)
23:46:19  * travis-cijoined
23:46:19  <travis-ci>[travis-ci] rackspace/pkgcloud#68 (userAgent - b3fb938 : Ken Perkins): The build passed.
23:46:19  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/commit/b3fb938ea0a4
23:46:19  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7069992
23:46:19  * travis-cipart
23:47:47  * admc1joined
23:49:26  * Hounddogquit (Ping timeout: 252 seconds)
23:49:31  * jamundquit (Quit: jamund)
23:49:32  * arushjoined
23:49:38  * cesconixquit (Quit: Computer has gone to sleep.)
23:53:16  * travis-cijoined
23:53:16  <travis-ci>[travis-ci] rackspace/pkgcloud#69 (userAgent - 7c21b49 : Ken Perkins): The build passed.
23:53:16  <travis-ci>[travis-ci] Change view : https://github.com/rackspace/pkgcloud/compare/b3fb938ea0a4...7c21b4965e78
23:53:16  <travis-ci>[travis-ci] Build details : http://travis-ci.org/rackspace/pkgcloud/builds/7070050
23:53:16  * travis-cipart
23:57:23  <rvagg>jcrugzz: @wolfeidau is working on graphite+levelup fyi
23:57:52  <jcrugzz>rvagg: Ohhhh link?
23:58:38  <rvagg>jcrugzz: ping him in #node.js, I don't know if he has anything public yet; he's working with ninjablocks now and is a total low-level & data nerd, loves stats, graphing, etc. etc.
23:58:45  <jcrugzz>rvagg: cause ideally i do not want to deal with a django server to run graphite and use its custom db shenanigans
23:58:48  <jcrugzz>word
23:58:49  * Nodejitsu-Githubjoined
23:58:49  * Nodejitsu-Githubpart
23:58:53  <jcrugzz>thanks for the heads up :D
23:58:54  <rvagg>perhaps you can collaborate