James Massardo - Geek of all things Technology

TravisCI Integration


Let the continuous integration begin! It took a little tinkering (mostly around getting the FTP upload to work), but I have TravisCI working with GitHub. I’m planning to detail out the process in a future post.

Basic Jeykll!


I guess I should blog some of the stuff I’m tinkering with so I don’t forget what I’m learning. I’m going to start at the base and log a few bits and commands about getting started with Jekyll.

First off, you need to install Jekyll. I’m currently using a Mac and I have the full build of Ruby installed for some Chef tinkering so I was able to follow the Jekyll Quickstart. I did have to change the install path as described on the Jekyll Troubleshooting page.

Ok, hopefully you got it installed so let’s actually do something with it.

# Install Jekyll and Bundler gems through RubyGems
~ $ gem install jekyll bundler

# Create a new Jekyll site at ./myblog
~ $ jekyll new myblog

# Change into your new directory
~ $ cd myblog

# Build the site on the preview server
~/myblog $ bundle exec jekyll serve

# Now browse to http://localhost:4000

(Yeah, I know, looks familar, eh? That’s cause I copied it straight from the Quickstart guide… It works, why reinvent the wheel…)

Next is to create a post.

# Create post file using the following format
~/myblog $ touch _posts/2017-06-05-basic-jekyll.md

From there, add your header and start writing. Post Docs

Dear Future Self


I met a lot of really awesome people at ChefConf. One guy, named Daniel, and I were joking about blogging stuff and we said we should start a blog named Dear Future Self. Technologists come in contact with so much information, there’s no way anyone can remember it all. A lot of the stuff on this blog is literally so I don’t have to remember everything.

So Dear Future self, please enjoy all this stuff :)

New Blog!


So I decided to change blogging tools again. I’ve been playing with some DevOps type tools and I needed something a little more real world for a test, so why not the website. I’m setting up some CI (Continuous Integration) tools to watch Github. Anytime there’s a new commit, that will trigger the CI tool to run prep the new code for deployment, run some automatic tests, deploy the new code, and finally notify me that it’s done.