15:31:08  * mmaleckitopic: Nodejitsu | Cloud status: our latency is down to nominal levels again. All systems go! | Support hours Mon-Fri 9am to 8pm EST
15:32:08  <waygee>Hi folks, my application is crash looping. Hoping someone can help. When I first deploy the application, everything works fine, after some time (a day or so) it crashes with: [09/11 07:24:58 UTC][err] Error: Redis connection to nodejitsudb7619463948.redis.irstack.com:6379 failed – connect ECONNREFUSED
15:32:08  <waygee>[09/11 07:24:58 UTC][err] at RedisClient.on_error (/opt/run/snapshot/package/node_modules/redis/index.js:163:24)
15:32:10  <waygee>[09/11 07:24:58 UTC][err] at Socket. (/opt/run/snapshot/package/node_modules/redis/index.js:86:14)
15:32:11  <waygee>[09/11 07:24:58 UTC][err] at Socket.EventEmitter.emit (events.js:96:17)
15:32:13  <waygee>[09/11 07:24:58 UTC][err] at Socket._destroy.self.errorEmitted (net.js:329:14)
15:32:14  <waygee>[09/11 07:24:58 UTC][err] at process.startup.processNextTick.process._tickCallback (node.js:245:9)
15:32:16  <waygee>[09/11 07:24:58 UTC][out] Listening on port 80…
15:32:17  <waygee>[09/11 07:24:58 UTC][out] Server initialization took 649 milliseconds
15:32:19  <waygee>[09/11 07:24:58 UTC][err] throw arguments1; // Unhandled ‘error’ event
15:32:20  <waygee>[09/11 07:24:58 UTC][err]
15:32:22  <waygee>[09/11 07:24:58 UTC][err] events.js
15:32:23  <waygee>[09/11 07:24:58 UTC][out] Starting application server
15:32:23  <waygee>[09/11 07:24:59 UTC][out] Using nodejitsu-foundation.settings.js file
15:33:23  <waygee>I think Redis connection is timing out, but not sure how to prevent that from happening. This happened with ~12 hours of no activity
15:34:35  * ChrisMathesonquit (Ping timeout: 245 seconds)
15:35:30  * davidbanhamquit (Ping timeout: 264 seconds)
15:36:19  <nathan7>waygee: Hey
15:36:39  <nathan7>waygee: That's our redis load balancer having some issues, we're working on resolving that
15:36:44  * gr2m_part ("Textual IRC Client: www.textualapp.com")
15:38:00  <waygee>wow really? any eta on this?
15:39:52  <nathan7>Not really, no.
15:40:14  <nathan7>(no ETA that is)
15:41:12  * cronopiojoined
15:43:29  <waygee>wow so that is making Redis completely unusable for right now
15:44:29  * daviddiasquit (Remote host closed the connection)
15:44:32  * sicularsjoined
15:44:40  <waygee>would it help to use a cron job that keeps the Redis connection active every hour. Would that help resolve the issue?
15:45:00  * daviddiasjoined
15:46:07  * Slaytors_joined
15:46:13  <waygee>Any workarounds or options?
15:46:31  * andreypoppjoined
15:47:18  * Slaytorsonquit (Ping timeout: 264 seconds)
15:47:43  <waygee>Is it something that is actively being worked on, or is it going to take days, weeks, months?
15:48:22  * Slaytorsonjoined
15:48:52  <nathan7>waygee: It should auto-reconnect
15:49:27  * daviddiasquit (Ping timeout: 260 seconds)
15:50:27  * daviddiasjoined
15:50:51  * alx_quit (Ping timeout: 245 seconds)
15:51:07  <waygee>ok, it doesn't appear to be doing so, are there any options I can pass in when I make the initial connection to Redis?
15:52:04  * Slaytors_quit (Ping timeout: 264 seconds)
15:54:46  * NodeJSDeveloperjoined
15:54:46  * NodeJSDeveloperquit (Client Quit)
15:55:27  * leichtgewichtquit (Remote host closed the connection)
15:56:06  * devdazedquit (Quit: Bye)
15:56:35  * benjaminbenbenquit (Ping timeout: 256 seconds)
15:57:27  * jonykrausequit (Read error: Operation timed out)
15:59:43  * devdazedjoined
16:00:48  * aus3ysjoined
16:01:00  * aus3ysquit (Client Quit)
16:04:21  * sreeixjoined
16:05:54  * jetiennejoined
16:21:47  * happycloudjoined
16:22:04  * happycloudpart
16:27:05  * thepumpkinjoined
16:28:02  * jonicjoined
16:28:35  * langprovingquit (Ping timeout: 250 seconds)
16:28:42  <jonic>Hey, anyone here actually from Nodejitsu?
16:31:24  <jonic>No one? Nice to know we're being looked after, isn't it?
16:31:27  * davidbanhamjoined
16:32:02  * brianruejoined
16:32:40  <cronopio>jonic: actually im not in support hours, but maybe I can help you
16:34:13  <jonic>@cronpio Thanks! Nice to finally get hold of someone! :) And thanks for taking some time out of your non-working hours, too!
16:34:37  <jonic>Basically I've been unable to get hold of support with a question I had about continually failed deploys and a now non-functioning Github hook.
16:34:54  * jetiennequit (Ping timeout: 264 seconds)
16:35:04  <jonic>I stuck my original email in this gist: https://gist.github.com/Jonic/6494400 - and asked someone on Twitter to take a look, but that's apparently been ignored too!
16:35:29  <jonic>I don't want to be a pain in the arse, but I'm a new customer and I'm just trying to make sure I'm with the right service - it's just not feeling like it right now :)
16:35:38  <jonic>That was meant to be a :( - you get what I mean.
16:35:50  * davidbanhamquit (Ping timeout: 245 seconds)
16:36:26  <cronopio>ok, so lets do some minimal tests to see what wrong is happend
16:36:37  <cronopio>the deploys should be working fine now
16:36:59  <cronopio>first of all, cd into your project and run `npm start`
16:37:13  <cronopio>check that your app is running locally and is not crashing or something
16:37:27  <cronopio>also remember that in our cloud your app run in Production mode
16:37:31  * travis-cijoined
16:37:31  <travis-ci>[travis-ci] mheap/winston#1 (master - f3b7b47 : Michael Heap): The build has errored.
16:37:31  <travis-ci>[travis-ci] Change view : https://github.com/mheap/winston/compare/ba3b575112e2...f3b7b47db1de
16:37:31  <travis-ci>[travis-ci] Build details : http://travis-ci.org/mheap/winston/builds/10511960
16:37:31  * travis-cipart
16:37:48  <jonic>Yeah, they seem to be working well enough now. The app works fine locally, and if I manually deploy through Terminal sometimes it works, sometimes it doesn't - no apparent reason why!
16:37:59  <cronopio>so try to run in production mode locally too, something like NODE_ENV=production or other stuff according to your framework
16:38:17  <jonic>Just my Github hook being ignored now. It was working a week ago, and testing it says that it's working fine, but it's not picking up my merges into Master anymore.
16:38:50  <cronopio>jonic: the Github hook has been some issues that we are working on, but not finished
16:38:57  <cronopio>jonic: lets try using jitsu
16:39:37  <cronopio>also, now use jitsu deploy --debug to get more information
16:39:47  * Samuel_Roldanquit (Quit: Samuel_Roldan)
16:40:13  <jonic>Runs fine locally when I set NODE_ENV to production
16:40:16  * jbprosjoined
16:40:16  * joshsmithjoined
16:40:27  <jonic>Trying jitsu deploy now
16:40:47  <cronopio>ok, afterwards past all the output to gist.github.com
16:42:19  <jonic>jitsu needs to update - one sec
16:43:10  * jetiennejoined
16:45:23  * joeybakerquit (Quit: Computer has gone to sleep.)
16:45:51  * andreypoppquit (Quit: andreypopp)
16:47:16  * jbprosquit (Ping timeout: 264 seconds)
16:47:50  * andreypoppjoined
16:48:43  * benjaminbenbenjoined
16:49:02  <jonic>Ok deploying now!
16:49:03  * daviddiasquit (Remote host closed the connection)
16:49:32  * daviddiasjoined
16:50:00  * frenchto1stquit (Ping timeout: 245 seconds)
16:50:23  * _shapsquit (Remote host closed the connection)
16:50:33  * _shapsjoined
16:50:44  <jonic>You still there cronopio? My jitsu deploy worked fine just now.
16:50:55  <cronopio>jonic: cool
16:51:06  * jetiennequit (Ping timeout: 276 seconds)
16:51:41  <jonic>It was 50/50 whether or not it worked before, so it's cool if you've sorted that out. There was no mention of there being problems on your status page though, nor have I seen anything about Github deploys being broken.
16:51:50  <cronopio>please take some patience please with the Github hook, and the stability of deploys, we are working hard to make sure that never happend that happend last two weeks
16:52:08  <cronopio>jonic: please see blog.jit.su
16:52:31  <cronopio>jonic: this one http://blog.jit.su/recent-instability-and-choosing-the-right-cloud
16:53:21  * protometajoined
16:54:03  <jonic>Cool, well that was published after I sent my first email about it, so I still kind of feel like even just a note on the status page would have been handy! And there's still nothing on it about the Github thing!
16:54:06  <cronopio>jonic: I saw on logs that your app is crashing at sometime
16:54:22  * daviddiasquit (Ping timeout: 256 seconds)
16:54:38  <jonic>I'm glad apps are reliably deploying now, but your Twitter account seems to be far too quiet!
16:55:18  * _shapsquit (Ping timeout: 264 seconds)
16:55:25  <jonic>Yeah I fixed any bugs that caused crashes and redeployed each time I saw one. I'm still kind of new to Node!
16:56:14  <jonic>Thanks for your help anyway. I could have been spared a lot of annoyance if your status page or Twitter account just said you were experiencing problems with Github! Thanks for taking the time out to help me all me the same :)
16:56:34  * daviddiasjoined
16:56:36  <cronopio>if your app continuously is crashing we can do too much to start it
16:57:09  * fb55quit (Remote host closed the connection)
16:57:25  <cronopio>jonic: yeah, apologies about that, feel free to join here anytime. We are here to try to help you out
16:57:44  <cronopio>here is the more realtime communication in problems case
16:57:46  * fb55joined
16:58:15  <jonic>Well it was good ta actually get hold of someone! Gotta run, but thanks again :)
16:58:25  <cronopio>jonic: cheers!
16:59:16  * jonicquit (Quit: Page closed)
16:59:42  * jetiennejoined
16:59:52  * jmar777quit (Read error: Connection reset by peer)
17:00:08  * jonykrausejoined
17:00:17  * jmar777joined
17:01:13  * TooTallNatejoined
17:01:56  <protometa>Anyone know why I might be getting a coffeescript error on deploy that I'm not getting in dev?
17:01:57  * fb55quit (Ping timeout: 248 seconds)
17:02:32  * jcrugzzjoined
17:03:02  <cronopio>protometa: mmm... let see that error, should be working
17:03:26  * SirFunkquit (Ping timeout: 240 seconds)
17:03:29  <protometa>server.coffee:25:1: error: unexpected INDENT
17:03:50  * InconceivableBjoined
17:04:12  <protometa>But it always occurs at 25:1 even if if that line is not indented or I completely rearrange the code...
17:05:27  * SirFunkjoined
17:09:59  * jahajoined
17:11:18  <protometa>Have you been having this sort of trouble with deploys lately?
17:12:03  <cronopio>protometa: not that I am aware of
17:12:06  * jetiennequit (Ping timeout: 264 seconds)
17:12:19  * frenchto1stjoined
17:13:17  <cronopio>protometa: I guess the only differences could be the coffee version in our cloud with yours...
17:13:30  * thepumpkinquit (Remote host closed the connection)
17:13:56  <cronopio>protometa: or even weird a endline or end of file with conflicts on SunOS
17:14:52  * Slaytors_joined
17:14:58  * Slaytorsonquit (Read error: Connection reset by peer)
17:15:22  <protometa>ok I can try your version of coffeescript. which is it?
17:17:09  <protometa>I've tried copying the code to a new file as well, moving the code all the way past line 25, but still the unexpected INDENT at 25:1... it's weird.
17:20:13  * bzooquit (Remote host closed the connection)
17:20:14  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
17:20:49  * bzoojoined
17:21:12  * bzooquit (Read error: Connection reset by peer)
17:21:38  * bzoojoined
17:22:04  * Slaytorsonjoined
17:23:54  <jcrugzz>protometa: we have the latest version of coffeescript running, which i believe is 1.6.3?
17:24:28  * Slaytors_quit (Ping timeout: 264 seconds)
17:26:40  <protometa>ok I'm already using that version.
17:27:58  * Eshjoined
17:28:08  * thealanwattsriotjoined
17:28:36  <Esh>Hi, im havin internal server error when tryin to deply my app any suggestions?
17:29:57  * Samuel_Roldanjoined
17:32:02  * davidbanhamjoined
17:36:47  * davidbanhamquit (Ping timeout: 260 seconds)
17:37:19  * Slaytors_joined
17:37:25  * frenchto1stquit (Ping timeout: 268 seconds)
17:38:03  * emilianocquit (Quit: Leaving.)
17:38:25  * tylerstalderjoined
17:38:48  * alxjoined
17:40:15  * alxquit (Remote host closed the connection)
17:40:17  * Slaytorsonquit (Ping timeout: 256 seconds)
17:40:48  * sberrymanquit (Read error: Connection reset by peer)
17:41:23  * stevemanueljoined
17:41:37  * daviddiasquit (Remote host closed the connection)
17:42:06  * daviddiasjoined
17:42:29  * indexzerojoined
17:44:15  * sberrymanjoined
17:45:46  * joeybakerjoined
17:46:31  * daviddiasquit (Ping timeout: 256 seconds)
17:49:11  * Eshquit (Ping timeout: 250 seconds)
17:51:07  * andy27joined
17:51:53  * daviddiasjoined
17:52:14  <andy27>hi there. I am trying to connect to my mongolab through my terminal, and I have a question about it. Should I simply be using this syntax? mongo --username <user> --password <pass> --host <host> --port <port> with the values shown on my database page?
17:55:20  * alxjoined
17:55:25  * sreeixquit (Read error: Connection reset by peer)
17:56:19  * espiraljoined
18:01:53  <protometa>You should be able to just use the connection string from your databases page.
18:02:45  <andy27>protometa: thank you. And if I want to do it from my terminal? how would i log in?
18:03:28  <protometa>Just paste that string after the mongo command.
18:03:58  * Slaytorsonjoined
18:04:10  * daviddiasquit (Ping timeout: 245 seconds)
18:04:20  <jcrugzz>Esh: run a `jitsu deploy --debug` and gist the output
18:04:34  * Slaytors_quit (Read error: Connection reset by peer)
18:04:37  * johnmartyjoined
18:05:41  <protometa>andy27: Oops sorry. The mongo command takes username and password arguments...
18:05:58  * daviddiasjoined
18:06:26  * alxquit (Remote host closed the connection)
18:07:16  <protometa>Go to terminal and use 'jitsu databases list'
18:08:23  <protometa>Then get connection info on the database you want with 'jitsu databases get <Database Name>'
18:09:13  * andreypoppquit (Quit: andreypopp)
18:09:15  <protometa>It will show you the exact command to connect to your database in the terminal with mongo.
18:10:01  <andy27>Thank you. The jitsu databases list is so far working
18:10:26  <joeybaker>hello – I'm looking for some help with ssl certs on ubntjoey/uwn. https was working great, and now visiting our url, goubiquiti.com, throws all kinds of warnings which make it look like the wrong certs are being served.
18:10:29  <andy27>Now I'm just working on accessing the collections
18:10:43  * daviddiasquit (Ping timeout: 268 seconds)
18:11:12  * sreeixjoined
18:11:18  * daviddiasjoined
18:12:24  <andy27>Yes. It works. Thank you very much.
18:12:33  * thepumpkinjoined
18:12:41  <andy27>I would never have figured it out by myself :)
18:13:30  <protometa>No problem.
18:14:30  <jcrugzz>joeybaker: can you try re-uploading the certs?
18:14:36  <jcrugzz>or cert rather
18:14:50  <joeybaker>jcrugzz: have done so ~5 times. Should I try again?
18:15:15  <jcrugzz>joeybaker: try it one more time
18:15:40  <joeybaker>jcrugzz: okay, gimme 1 min :)
18:15:41  * andy27quit (Quit: Page closed)
18:15:42  * tonistjoined
18:16:23  <protometa>Doesn't nodejitsu handle certs and https for you?
18:17:49  * daviddiasquit (Remote host closed the connection)
18:17:57  <nathan7>protometa: Yep
18:18:22  * daviddiasjoined
18:18:37  <joeybaker>protometa: I've got my own domain, which requires my own certs :)
18:18:46  <protometa>oh ok
18:20:50  * jcrugzzquit (Ping timeout: 245 seconds)
18:22:59  * daviddiasquit (Ping timeout: 260 seconds)
18:24:28  * indexzeroquit (Quit: indexzero)
18:30:43  * daviddiasjoined
18:32:35  * davidbanhamjoined
18:35:02  * jcrugzzjoined
18:35:08  * sreeixquit (Quit: sreeix)
18:36:50  * alxjoined
18:37:40  * davidbanhamquit (Ping timeout: 264 seconds)
18:38:45  * DTrejojoined
18:38:54  * sreeixjoined
18:39:00  * tylerstalderquit (Quit: Computer has gone to sleep.)
18:42:06  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
18:42:29  * protometaquit (Ping timeout: 250 seconds)
18:43:58  * alxquit (Read error: No route to host)
18:44:06  * alxjoined
18:46:00  * ChrisMathesonjoined
18:52:01  * daviddiasquit (Remote host closed the connection)
18:52:30  * daviddiasjoined
18:52:43  * sicularsquit (Quit: siculars)
18:54:13  * Slaytors_joined
18:55:45  * frenchto1stjoined
18:55:57  * Slaytorsonquit (Ping timeout: 240 seconds)
18:57:28  * daviddiasquit (Ping timeout: 264 seconds)
18:58:13  * jcrugzzquit (Ping timeout: 248 seconds)
19:06:10  * jcrugzzjoined
19:06:30  * johnmartyquit (Quit: Leaving.)
19:06:39  * frenchto2stjoined
19:06:39  * Slaytorsonjoined
19:08:48  * alxquit (Remote host closed the connection)
19:09:10  * frenchto1stquit (Ping timeout: 245 seconds)
19:09:35  * Slaytors_quit (Ping timeout: 245 seconds)
19:10:31  * daviddiasjoined
19:14:48  * frenchto1stjoined
19:15:00  * frenchto2stquit (Ping timeout: 245 seconds)
19:15:36  * thealanwattsriotjoined
19:17:04  * indexzerojoined
19:17:26  * johnmartyjoined
19:23:03  <indexzero>mmalecki jcrugzz yt?
19:23:18  * DTrejoquit (Remote host closed the connection)
19:23:21  <jcrugzz>indexzero: sup
19:24:01  * daviddiasquit (Remote host closed the connection)
19:24:13  <indexzero>nm, how was yoga yesterday?
19:24:30  * daviddiasjoined
19:24:43  * daviddiasquit (Read error: Connection reset by peer)
19:25:28  <jcrugzz>indexzero: good, was getting into some of the teachings
19:25:43  * topwobblejoined
19:25:58  * daviddiasjoined
19:26:01  * daviddiasquit (Remote host closed the connection)
19:26:49  * jbprosjoined
19:26:59  * andreypoppjoined
19:29:43  * jonykrau_joined
19:30:29  * jonykrausequit (Read error: Operation timed out)
19:33:09  * davidbanhamjoined
19:33:33  * joeybakerquit (Quit: Computer has gone to sleep.)
19:33:34  * tonistquit (Quit: tonist)
19:33:59  * jonykrausejoined
19:36:06  * jonykrau_quit (Ping timeout: 264 seconds)
19:36:06  * jcrugzzquit (Ping timeout: 264 seconds)
19:36:33  * ChrisMathesonquit
19:36:52  * Antonio__joined
19:37:39  * davidbanhamquit (Ping timeout: 260 seconds)
19:38:05  <Antonio__>hello - is support available here?
19:39:20  * jcrugzzjoined
19:44:21  * defunctzombie_zzchanged nick to defunctzombie
19:46:07  * DTrejojoined
19:47:18  <nathan7>Antonio__: yep
19:47:56  * alxjoined
19:49:49  * tylerstalderjoined
19:52:53  * alxquit (Ping timeout: 256 seconds)
19:54:10  * joeybakerjoined
19:55:17  * Antonio__quit (Ping timeout: 250 seconds)
19:58:39  * jcrugzzquit (Ping timeout: 240 seconds)
19:59:40  * waygeequit (Quit: waygee)
19:59:43  * topwobblequit (Quit: topwobble)
20:00:15  * waygeejoined
20:02:59  * julianduquejoined
20:04:12  * topwobblejoined
20:04:12  * jcrugzzjoined
20:06:59  * protometajoined
20:07:26  <protometa>Hey I think I may have found a bug...
20:08:05  <julianduque>protometa: what kind of bug?
20:08:45  <protometa>That coffeescript error was reporting the wrong location.
20:09:47  <julianduque>protometa: what do you mean?
20:10:18  <nathan7>protometa: We pretty much fire the stock coffee binary
20:10:40  <nathan7>I'm working on reworking this stuff so you can also just ship your own coffee-script as dependency, which takes precedence
20:10:53  <protometa>It reported `server.coffee:25:1: error: unexpected INDENT`...
20:11:38  <protometa>The line it showed was not indented and it always occurred at line 25:1...
20:11:54  <nathan7>CoffeeScript bug I'm afraid
20:11:57  <protometa>The error was actually in one of my many required files.
20:11:57  <nathan7>we can't change a lot about that
20:12:17  <protometa>I only found it by dismantling my code and deploying it bit by bit.
20:12:26  <nathan7>:(
20:13:03  <protometa>Coffeescript was reporting the wrong location?
20:13:06  * Slaytors_joined
20:13:42  <protometa>I only ran into the error on deploying to Jitsu so... I was sure what was happening.
20:13:59  <nathan7>Maybe we're behind on CoffeeScript versions
20:14:28  <nathan7>the issue with something like this without a declared version that isn't a dep can't be easily upgraded in case of breaking changes
20:14:31  <protometa>I wasn't* sure that is.
20:15:17  * Slaytorsonquit (Ping timeout: 268 seconds)
20:16:05  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:16:22  * sreeixquit (Quit: sreeix)
20:16:37  * jcrugzzquit (Ping timeout: 248 seconds)
20:21:02  * stevemanueljoined
20:23:17  * topwobblequit (Quit: topwobble)
20:33:47  * davidbanhamjoined
20:34:55  * jmar777quit (Remote host closed the connection)
20:37:42  * jbprosquit (Quit: jbpros)
20:38:38  * davidbanhamquit (Ping timeout: 264 seconds)
20:45:30  <rossk>mmalecki: I'm back!
20:55:09  <protometa>MY BAD... my package coffeescrpt was up to date by my global coffeescript wasn't...
20:55:28  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:57:49  * stevemanueljoined
20:58:43  * doubletapjoined
21:00:10  * jonykrausequit (Remote host closed the connection)
21:07:55  * fb55joined
21:10:41  * jcrugzzjoined
21:12:31  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:13:23  * topwobblejoined
21:18:37  * alxjoined
21:20:06  <mmalecki>rossk: omg hai, how was it?
21:21:31  * Slaytors_quit (Read error: Connection reset by peer)
21:22:01  * Slaytorsonjoined
21:23:27  * alxquit (Ping timeout: 276 seconds)
21:24:06  * Samuel_Roldanquit (Ping timeout: 256 seconds)
21:34:16  * davidbanhamjoined
21:38:59  * davidbanhamquit (Ping timeout: 260 seconds)
21:39:55  * frenchto2stjoined
21:40:28  * oneyedmikejoined
21:42:32  * doubletapquit (Quit: Leaving.)
21:42:49  * frenchto1stquit (Ping timeout: 256 seconds)
21:43:11  * DTrejoquit (Remote host closed the connection)
21:44:29  <oneyedmike>hello
21:45:13  <julianduque>oneyedmike: hello :)
21:45:19  <oneyedmike>I'm looking for a little help with "Continuous Deployment with Github and Nodejitsu"
21:45:36  * kevino80quit (Remote host closed the connection)
21:46:05  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:46:21  <julianduque>oneyedmike: how can I help?
21:46:29  <oneyedmike>As I understand it, after setting up the hook in github, anything I push to the specified branch should be depolyed
21:46:39  <oneyedmike>is that correct?
21:46:47  * topwobblequit (Quit: topwobble)
21:47:02  * frenchto2stquit (Ping timeout: 240 seconds)
21:47:38  * frenchto1stjoined
21:47:46  <oneyedmike>I'm basing this off of http://blog.nodejitsu.com/github-continuous-deployment
21:49:06  * DTrejojoined
21:49:10  <julianduque>oneyedmike: We published this guide: https://www.nodejitsu.com/getting-started-with-github/
21:50:39  <julianduque>oneyedmike: but, the service is unstable right now, it fails on some cases, we are still investigating and working on a fix
21:50:57  <oneyedmike>ok
21:51:30  <oneyedmike>so is it even worth trying to make work right now?
21:52:36  <julianduque>oneyedmike: it's a public or private repo?
21:52:55  <oneyedmike>at the moment private
21:53:15  <oneyedmike>it's our webapp so it will likley stay that way
21:53:23  <oneyedmike>does it have to be public?
21:54:04  <julianduque>oneyedmike: no it can be private
21:54:31  <oneyedmike>the guide that you sent me is different then the one i sent
21:54:31  <julianduque>oneyedmike: and, what is the size of the snapshot? (do `npm pack` and check the size of the *.tgz file)
21:55:33  * stevemanueljoined
21:56:07  <oneyedmike>it's only 1.3k
21:56:24  * stevemanuelquit (Client Quit)
21:56:25  * frenchto1stquit (Ping timeout: 256 seconds)
21:57:08  <julianduque>oneyedmike: you can try, following the guide I've sent to you (make sure put your token not your password on the github service settings)
21:57:57  * frenchto1stjoined
21:58:11  <oneyedmike>and don't set the branch or endpoint?
21:59:08  <julianduque>oneyedmike: default is to master, you can set your own branch, if you want create a `test` branch and see if it works
21:59:27  <oneyedmike>also- where do i find the token?
22:01:07  * CoverSlidejoined
22:02:05  * frenchto1stquit (Ping timeout: 245 seconds)
22:03:00  * frenchto1stjoined
22:03:58  <oneyedmike>i think I found them.. the question is do i use the jitsu or webops
22:04:26  <julianduque>oneyedmike: you can use both, I prefer jitsu :)
22:05:25  * johnmartyquit (Ping timeout: 248 seconds)
22:06:26  * waygeequit (Quit: waygee)
22:08:03  * frenchto2stjoined
22:08:12  <oneyedmike>ok- cool. thanks for your help ;)
22:08:21  * frenchto1stquit (Ping timeout: 245 seconds)
22:16:59  * oneyedmikequit (Ping timeout: 250 seconds)
22:17:49  * jahaquit (Quit: Leaving.)
22:19:36  * frenchto2stquit (Ping timeout: 245 seconds)
22:20:45  * InconceivableBquit (Quit: Computer has gone to sleep.)
22:21:25  * frenchto1stjoined
22:27:15  * frenchto1stquit (Ping timeout: 268 seconds)
22:27:53  * CoverSlidequit (Quit: Lost terminal)
22:28:03  * frenchto1stjoined
22:28:28  * RushPL_changed nick to RushPL
22:33:14  * frenchto1stquit (Ping timeout: 264 seconds)
22:34:23  * frenchto1stjoined
22:34:54  * davidbanhamjoined
22:39:10  * davidbanhamquit (Ping timeout: 245 seconds)
22:39:16  <rossk>mmalecki: it couldn't have gone better
22:39:25  <rossk>it was great seeing so many friends and family
22:40:06  * bzooquit (Remote host closed the connection)
22:40:38  * bzoojoined
22:41:44  * frenchto1stquit (Ping timeout: 240 seconds)
22:41:46  * frenchto2stjoined
22:42:38  * thepumpkinquit (Remote host closed the connection)
22:45:01  * bzooquit (Ping timeout: 245 seconds)
22:58:02  * Slaytorsonquit (Remote host closed the connection)
22:58:37  * Slaytorsonjoined
22:58:42  * frenchto2stquit (Ping timeout: 268 seconds)
22:59:46  * defunctzombiechanged nick to defunctzombie_zz
22:59:58  * c4miloquit (Remote host closed the connection)
23:01:00  * defunctzombie_zzchanged nick to defunctzombie
23:03:11  * mdedetrichjoined
23:03:34  * stevemanueljoined
23:09:14  * defunctzombiechanged nick to defunctzombie_zz
23:14:16  * thepumpkinjoined
23:19:30  * alxjoined
23:24:28  * alxquit (Ping timeout: 264 seconds)
23:28:20  * c4milojoined
23:29:12  * c4miloquit (Remote host closed the connection)
23:29:20  * c4milojoined
23:32:47  * Slaytors_joined
23:33:18  * Slaytorsonquit (Ping timeout: 256 seconds)
23:35:27  * davidbanhamjoined
23:36:17  * benjaminbenbenquit (Quit: benjaminbenben)
23:36:19  * johnmartyjoined
23:36:25  * joeybakerquit (Quit: Computer has gone to sleep.)
23:38:27  * Samuel_Roldanjoined
23:40:01  * davidbanhamquit (Ping timeout: 268 seconds)
23:41:26  * johnmarty1joined
23:42:02  * davidbanhamjoined
23:44:30  * johnmartyquit (Ping timeout: 264 seconds)
23:50:17  * Shapsquit (Remote host closed the connection)
23:55:52  * andreypoppquit (Quit: andreypopp)
23:58:30  * andreypoppjoined