[00:03:35] wolfcore: yeah, ubuntu LTS [00:03:57] i've got pretty good unicode support, i just don't have those emojis apparently [00:05:02] wfh privilege is being to sip craft beer while going through the defect backlog [00:05:30] and nibble on smoked meat for the sake of pairing [00:06:30] mostly IPAs and belgian quads [00:34:13] *** Quits: coldsauce (180e92f9@gateway/web/cgi-irc/kiwiirc.com/ip.24.14.146.249) (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) [01:04:26] la banquise. is the jawn. [02:56:14] *** Quits: emo-bot (~emo-bot@saskia.igm.rit.edu) (Remote host closed the connection) [03:01:50] *** Joins: Ritwik_ (~Ritwik@2600:1016:b025:53a8:c06b:c57:2817:c747) [03:05:14] *** Quits: Ritwik (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) (Ping timeout: 256 seconds) [03:10:21] *** Joins: emo-bot (~emo-bot@saskia.igm.rit.edu) [03:34:27] *** Joins: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) [03:37:30] *** Quits: Ritwik_ (~Ritwik@2600:1016:b025:53a8:c06b:c57:2817:c747) (Ping timeout: 260 seconds) [04:34:12] *** Quits: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) (Ping timeout: 256 seconds) [04:44:52] *** Joins: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) [04:51:12] *** Quits: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) (Ping timeout: 256 seconds) [04:59:53] *** Joins: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) [05:13:39] is there some HH subgroup for job advice, i.e. deciding between offers [05:16:08] *** Quits: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) (Ping timeout: 256 seconds) [06:44:53] *** Joins: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) [06:50:28] *** Quits: Ritwik__ (~Ritwik@eh-130-49-81-178.oakland.resnet.pitt.edu) (Read error: Connection reset by peer) [09:56:36] voting app source code is out https://github.com/wearehx/voting [09:56:36] Title: wearehx/voting · GitHub [09:56:47] it is partially broken though [10:45:12] StyleCI made a huge PR to fix my shitty code lol [11:01:01] goood morning! [11:03:37] hey [11:20:32] gsingh93: you have two days to deploy it flawlessly :p [11:25:39] and audit it, of course [12:32:36] *** Quits: Monie (~Monie@cowbot.jamonek.com) (Excess Flood) [12:32:48] *** Quits: yossarian-bot (~yossarian@104.131.177.124) (Ping timeout: 272 seconds) [12:32:52] *** Joins: Monie (~Monie@cowbot.jamonek.com) [12:32:56] *** Joins: yossarian-bot (~yossarian@104.131.177.124) [12:32:59] *** ChanServ sets mode: +v yossarian-bot [12:36:36] *** Quits: wilfriedE (~wilfriedE@bryn.justinwflory.com) (Ping timeout: 272 seconds) [12:36:46] *** Joins: wilfriedE (~wilfriedE@bryn.justinwflory.com) [13:21:11] *** Joins: coldsauce (180e92f9@gateway/web/cgi-irc/kiwiirc.com/ip.24.14.146.249) [13:34:35] *** Quits: coldsauce (180e92f9@gateway/web/cgi-irc/kiwiirc.com/ip.24.14.146.249) (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) [17:23:57] kk, voting app works now [17:24:12] gotta add the results endpoint and it's production ready [18:38:32] iangcarroll: let me know [18:38:38] should be able to mess with it today [18:39:03] well you can deploy it anytime [18:39:08] it works [18:42:24] do you think the heroku free plan should be good enough? [18:47:20] maybe [18:47:24] you might hit the 18hr cap [18:47:35] but you can adjust that on the fly, and I don't think it's active yet (??) [18:47:48] it might give you a few warnings first [18:48:04] but it needs little to no memory to run; gonna swap it over to nginx and it'll be fine [18:54:51] Well, that commit broke it. [18:57:18] Alright, fixed, uses nginx now. [21:44:05] iangcarroll: let's say the website goes over the 18h/day cap [21:44:14] do they immediately charge you $7? [21:44:19] no, it turns off [21:44:25] ah [21:44:31] and if you upgrade it to the "hobby" dyno tier it's prorated to the second [21:44:48] so you can upgrade just for 6hrs/day [21:45:07] i see [21:45:36] i'll just see how the free tier goes for a while [21:46:00] sounds good [21:46:05] i'll set it up in an hour or two [21:46:12] kk; let me know if something breaks [21:46:16] *when [21:55:35] holy hell sivoais how many github orgs are you in [21:58:13] iangcarroll: would you recommend deployment with github or the heroku git tools? [21:59:14] the former would be easier as it'd sync changes w/ heroku immediately with the gh repo [21:59:28] but you won't be able to modify any files privately [21:59:55] which shouldn't be a problem [22:00:58] iangcarroll: lol, most of them are my own... I needed to classify my repos by project or else I'd go crazy with 300 repos under my user :-P [22:01:37] lol, seems fair [22:36:34] iangcarroll: does heroku have support for composer applications out of the box? [22:36:51] it seems like it [22:37:00] ah, i forgot about that; you have to run `heroku buildpacks:set heroku/php` or it tries to use node [22:37:01] but i'm not sure it's working [22:37:05] ah [22:37:12] also: https://devcenter.heroku.com/articles/php-support [22:37:13] Title: Heroku PHP Support | Heroku Dev Center [22:37:14] hhvm support [22:37:30] yea, but they don't support PostgreSQL via PDO [22:37:40] they said they had a fix for it a year ago so kinda waiting [22:38:41] sorry, they said "soon" on march 10th [22:38:47] they being heroku [22:47:09] ok, so it's detected as php now [22:47:13] it should be live here: https://hackers-voting.herokuapp.com/ [22:47:13] Title: Unknown [22:47:16] when it's finished [22:47:46] wait it failed [22:50:31] iangcarroll: anyway to get the build log as a text file, or on the command line? [22:50:45] lol [22:51:04] you should be able to see it in the release history in dashboard.heroku [22:51:27] the build log is in a fucking text area [22:51:34] i can't easily copy and paste it [22:51:58] i had to select it all [22:51:59] lol [22:52:02] ctrl+a? [22:52:04] first world problems [22:52:06] no [22:52:08] because it's a text area [22:52:13] ctrl+a selects everything [22:52:25] http://pastie.org/private/vdfq33zlffohaxrqblwlg [22:52:26] Title: Private Paste - Pastie [22:52:28] when you click in a text area your browser doesn't only select things in it? [22:52:37] pretty sure mine does [22:52:50] nope [22:52:53] never seen that before [22:52:55] oh right there's an undocumented env variable lol [22:54:07] i was using https://github.com/getsentry/sentry to track exceptions [22:54:08] Title: getsentry/sentry · GitHub [22:54:28] i might just remove the dependency given you probably don't want stack traces sent to me [22:56:44] Pushed it [22:58:36] Fatal error: Class 'Jenssegers\Raven\RavenServiceProvider' not found [22:59:47] probably should have removed the reference to it after I removed it as a dependency [23:00:16] There we go (again) [23:02:35] have you seen this error before: 2015/12/20 04:01:10 [error] 96#0: *10 access forbidden by rule, client: 10.169.113.242, server: localhost, request: "GET /.git/HEAD HTTP/1.1", host: "hackers-voting.herokuapp.com", referrer: "https://hackers-voting.herokuapp.com/" [23:02:36] Title: Unknown [23:03:01] lol are you trying to access the git repo? [23:03:15] that's a chrome extension lol [23:03:26] didn't look at the path [23:03:28] so that's why you always find those errors [23:03:28] but it's still not working [23:03:34] https://hackers-voting.herokuapp.com/ [23:03:34] Title: Unknown [23:03:36] yea [23:03:40] my secret's out [23:03:42] i was thinking you just did it on every site [23:03:45] lolol [23:04:00] it wouldn't work anyway as nginx is pointing to the public dir and the git repo is a level before that, but it's probably an issue heroku blocked with all apps in case [23:04:42] you're gonna have to run heroku config:add APP_DEBUG=true to get a stacktrace [23:05:57] oh [23:06:00] i know what it is [23:06:09] you need to generate an app key and set it in APP_KEY [23:06:31] 32 chars A-Za-z0-9 [23:06:50] if you have php/the repo locally and composer deps installed you can run php artisan key:generate to generate one [23:10:03] dockerizing this would have been nice [23:10:20] you are dockerizing this by putting it into heroku :p [23:10:37] it's not dockerized locally [23:10:47] meaning i need to pollute my system with php crap [23:10:52] lol [23:11:02] just use like https://identitysafe.norton.com/password-generator/ [23:11:02] Title: Create Safe & Secure Passwords - Password Generator | Norton Identity Safe [23:11:37] i like how i'm the maintainer of this thing and i'm probably not going to have a locally running instance of it [23:11:42] haha [23:12:14] you can use laravel homestead too, which is a VM setup for laravel [23:12:37] do i use `heroku config:add` for this? [23:12:45] APP_KEY? yea [23:14:36] is APP_SECRET the same as what you called FACEBOOK_APP_SECRET in the readme? [23:14:44] what about APP_ID? do i prepend FACEBOOK_ to it? [23:15:18] do you mean the facebook app id/secret? [23:15:29] those go in FACEBOOK_APP_ID and FACEBOOK_APP_SECRET, yea [23:15:41] the random string you generate goes in APP_KEY [23:16:00] ah, right [23:19:44] README should be a bit more clear now. [23:22:17] what is the verify token? [23:22:38] ah, you also need to whitelist the oauth url [23:22:43] i hate oauth [23:23:00] When you create a webhook in the Facebook dev console, it makes you specify a random string (the verify token) that will be sent back to the server. [23:24:14] added the whitelist part to the readme [23:25:54] is there any convention for choosing a verify token? [23:26:10] should i randomly generate it or just choose something [23:27:31] random it is [23:27:50] Anything you want, I guess. [23:28:08] Though if you can guess it, the URL will return arbitrary data, so probably something long enough. [23:28:44] Luckily, I did add an escape function around the data the URL is told to return. [23:32:38] hmm [23:32:41] i'm still missing something [23:34:16] i don't see any errors in the logs [23:34:26] but it still says "Whoops, looks like something went wrong." [23:35:21] oh, let me turn that debug thing on [23:36:07] ah, postgres issues [23:37:08] iangcarroll: should postgres work automatically? [23:37:37] it sounds like a pg server isn't running [23:48:53] let me add all this to the readme lol [23:49:05] you have to migrate the db with `heroku run php artisan migrate --force` [23:57:58] Added term creation instructions to the readme, which might cause issues after migrating.