June 7, 2018

[21:18:50] pilgrimish: joins
[21:18:50] pilgrimish_: joins
[02:35:33] pilgrimish_: leaves
[02:35:33] pilgrimish: leaves
[09:26:19] pilgrimish: joins
[09:26:23] pilgrimish_: joins
[10:02:15] pilgrimish_: leaves
[10:02:15] pilgrimish: leaves
[10:02:43] pilgrimish: joins
[10:02:45] pilgrimish_: joins
[10:03:02] pilgrimish_: leaves
[10:03:02] pilgrimish: leaves
[10:03:34] pilgrimish_: joins
[10:03:34] pilgrimish: joins
[10:03:48] pilgrimish_: leaves
[10:03:49] pilgrimish: leaves
[10:04:19] pilgrimish: joins
[10:04:20] pilgrimish_: joins
[10:04:35] pilgrimish: leaves
[10:04:35] pilgrimish_: leaves
[10:04:58] pilgrimish: joins
[10:04:59] pilgrimish_: joins
[10:05:22] pilgrimish_: leaves
[10:05:22] pilgrimish: leaves
[10:05:52] pilgrimish_: joins
[10:05:52] pilgrimish: joins
[10:06:09] pilgrimish_: leaves
[10:06:09] pilgrimish: leaves
[10:06:37] pilgrimish: joins
[10:06:37] pilgrimish_: joins
[10:06:55] pilgrimish: leaves
[10:06:55] pilgrimish_: leaves
[11:37:13] tulsi[m]: @kenbolton how's gitlab been treating you? I've been meaning to move my repos from github (since before this whole MS bs happened) but I've heard that it's performance isn't great. Considering Gogs instead
[11:42:39] kenbolton[m]: tulsi: using a c4.large instance on aws, seems very snappy and responsive. of course, i'm probably not really putting too much load into it.
[11:43:16] tulsi[m]: ah so you're hosting yourself not using gitlabs service
[11:43:55] kenbolton[m]: so far, i really like it. gitlab-flavored markdown is compatible w/ org-mode. i'm migrating my jira issues. eventually, i'll move our CI/CD from jenkins.
[11:44:43] kenbolton[m]: yeah, sorry for that confusion. i'm using the gitlab 10 AMI to host it.
[11:45:02] kenbolton[m]: i'll be moving my personal stuff at some point, but not in a big hurry.
[11:45:35] kenbolton[m]: setting it up in AWS was trivial.
[11:55:56] gus_mustakas[m]: agreen I love that tweet.
[11:56:34] M_slack_digitals: had me crying 😂
[11:59:15] kenbolton[m]: note that the MS purchase was simply the final straw for my slow departure and that i'm not using the azure-based gitlab.com, but a gitlab AMI in AWS.
[12:03:06] gus_mustakas[m]: I also read this post on medium which I thought was a decent perspective...
[12:03:06] gus_mustakas[m]: https://medium.com/@ow/microsoft-acquiring-github-is-a-good-thing-heres-why-6a6a57eb83ac
[12:10:13] tulsi[m]: Yeah my big qualm with github is not that MS owns it. As a .Net developer for the past year I've seen first hand how MS has been embracing opensource. Props to them.
[12:10:13] tulsi[m]: My problem with github is that it's closed source. Why have a closed source tool in my toolbox when there are great open alternatives?
[12:11:54] kenbolton[m]: github is also the home of "brogrammer culture"; that and closed source were my beef.
[12:20:39] kenbolton[m]: oh, and electron. always electron.
[12:21:51] gus_mustakas[m]: What is brogrammer culture?
[12:22:49] kenbolton[m]: sexism
[12:26:00] tulsi[m]: kenbolton: If you don't mind me asking, what are you paying a month for that Gitlab AWS instance? I usually use digital ocean but an instance large enough to run Gitlab would run me $20 bucks. AWS any better than that?
[12:27:32] kenbolton[m]: $.10/hour on-demand.
[12:29:00] tulsi[m]: yeah so I'd probably be screwed by Digital Ocean's flat monthly rates
[12:30:31] kenbolton[m]: we'll drop that to $0.06/hour reserved.
[12:30:43] kenbolton[m]: about $40/month.
[12:30:58] kenbolton[m]: but it will replace two SaaS and one instance.
[13:24:26] kenbolton[m]: n.b. the instance that will be replaced is a t2.medium at about $.05/hour.
[13:26:29] kenbolton[m]: hmmm, c4.large and t2.medium have identical specs.... might revisit.
[13:53:21] tim[m]3: kenbolton is the bottleneck CPU or ram?
[14:16:18] kenbolton[m]: Idk, tim.
[14:54:50] tim[m]3: https://docs.gitlab.com/ee/install/requirements.html
[15:24:11] kenbolton[m]: I read somewhere in the gitlab docs that the ami should be run on c4.large.