Michael Blum

Developer from Chicago

Moving back to Github July 3, 2016

Coming back to the fold While setting up my own git server was a fun exercise, the truth is no open-source contributor or prospective employer will go hunting the web for your personal repository. In short, at least having your code on Github greatly increases the odds of your work seeing the light of day. To be sure, Gitlab has some great use cases that, as a single developer, I just don’t encounter:

Building a Blog Part 3 - Continuous Integration with Gitlab CI April 13, 2016

Why CI a simple blog? Just like we write automated unit tests for our applications, anything we’re pushing to the Web should be stable and we’re confident we didn’t break our site with an errant //JS or <HTML> tag. To do this, we’ll attach an integration service listening to our commits to the master branch. Choosing a Platform Since I’m running my blog outside of Github Pages, I can’t depend on integration servies such as Travis CI and Github’s ecosystem of integrations.

Building a Blog Part 2 - Git Server April 10, 2016

Why? There’s Github I’m interested in what GitLab is offering - a full featured Git server that supports many of the features found on GitHub: Pages Issue Tracking Pull Requests Private Repos (Gitlab is unlimited as opposed to the five I get on Github) and the list goes on. Webhooks One difference I saw was with the use of Web Hooks, the developer is responsible for maintaining a server to support their Webhooks.