Codeship is a fantastic tool to assist in all your continuous integration/deployment needs. Go support is provided out of the box however does not use aspects such as version locked dependencies out the box. When I happened to trial it out, I managed to get a working example of a Go setup including Glide dependencies. This post will provide you with a breakdown of how I managed to get this working. The example should be easily transferable to most other vendor tools such as Godep.

Test Settings

Our test settings need to do a few things.

1. Install Glide
2. Run glide install
3. Ensure dependencies are in $GOPATH
4. Run our tests

Let’s step through this line by line:

source /dev/stdin <<< “$(curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/languages/go.sh)"

First, we run this script that installs the version of Go declared in the GO_VERSION environment variable. This is not required for this tutorial, but can be helpful when using Go within Codeship.

go get github.com/Masterminds/glide

Then we have to install Glide via the go get command. This is the easiest way to install the dependency and automatically has it included in the PATH.

glide install

Now that glide is installed, we need to fetch all of our dependencies.

rsync -razC vendor/ $GOPATH/src/

Our final step in preparation is syncing the vendor directory into our GOPATH.

Now that we have all our version locked dependencies installed into our GOPATH we can run our desired test commands.

go vet -v $(glide novendor)
go test -v $(glide novendor)

If you have not previously used Glide, $(glide novendor) allows us to ignore the vendor directory when running our test commands.

All done. We now have version locked dependencies being used within our continuous integration platform.

Using Codeship with Go and Glide was originally published in OpenPixel on Medium, where people are continuing the conversation by highlighting and responding to this story.

For the past week or so I have been keeping a journal of my thoughts throughout the day. Although not a new idea by any means, I would love to share my experience.

Like most people, I have a lot going on in my life. Three months ago I started my own consulting company. Two months ago I became a first time father, which is easily the most terrifying and rewarding moment of my life. Amongst all this change, I found that I couldn’t find any time to reflect on my own thoughts and feelings. Previously, there always seemed to be the time to find a quiet place to sit down and think about what I had been doing and how I was feeling. This is certainly not the case anymore but I wouldn’t want to change it for anything. Instead, it was time to adapt and find new ways to achieve the same outcome.

Having never journaled before I wanted to find a process that was simple, easy to follow and provided value to reflect on in future days or weeks.

It is extremely simple, but allows me to see my progress throughout the day including what has held me back or pushed me on to achieve a lot. The Sleep and Overall scores are also great for reflection and can even be tallied and the end of the week to give an average score. Providing a time for each section of thoughts also assists you in tracking your progress throughout the day.

So far the journal has achieved a few things. My focus throughout the day is generally better, due to the small amounts of time I spend writing notes to look on later. If there is a frustrating moment, I try to note it down immediately so I can move on from it. The biggest thing for me is that I am getting a true sense of what motivates me and what makes me happy, something I have never really been able to achieve.

Any note taking tool will work, but I recommend [Evernote](https://www.evernote.com), [DayOne](http://dayoneapp.com/) or a similar tool. A few bonus features can be tagging people or places to see what has the biggest impact on your life.

An overview of the Flight framework by Twitter

I first tried Flight in March this year when I created a simple Todo app. After completing that, I didn’t look at Flight again until a month ago. I started using it for a personal project and after a few initial struggles I feel like it could be the long-term framework I have been looking for. The reason for this is summed up nicely on the Flight website:

It’s agnostic to how requests are routed, which templating language you use or even if you render your HTML on the client or the server.

Lift Off

Getting Flight set-up was easy. Using Bower, I installed the known requirements (es5-shim, jQuery, requirejs) and setup my first component.

define(function(require) {
  var defineComponent = require(“flight/lib/component”);
  return defineComponent(helloWorld);
  
  function helloWorld () {
    this.after("initialize", function() {
      alert("Hello World!");
    });
  }
});

Pretty simple, isn’t it. This is doing nothing more than using Flight’s Advice API to wrap the default “initialize” method and alert them once it’s ready. For this to run, you need to attach the component to the page.

require(["ui/helloWorld.js"], function(HelloWorldUI) {
  HelloWorldUI.attachTo(document);
});

Again, pretty simple. The attachTo method accepts a DOM element which becomes the context for the component.

Where Are My Models?

Flight does not handle models directly. The following is a quote from the Flight website:

It doesn’t prescribe or provide any particular approach to rendering or providing data to a web application

This means it is up the developer to choose the best approach for each application. Some approaches I have seen mentioned in regards to Flight are:

• No models (Objects and arrays. Wow!)
• laces.js

At this point I am leaning towards the modeless approach. Libraries such as Lodash provide enough utilities to make working with arrays and objects more than bearable. Some Mixins could easily be created to help manage anything that seems to be repeating. What is a mixin you ask? Great question.

Mixins

Mixins are the most powerful feature of Flight. They are plug and play scripts that help keep your code DRY. Mixins can be applied to both components or standard objects. Here is an example of a simple request Mixin that helps handle ajax. This can then be applied to a component like so:

var withRequests = require("mixins/withRequests");
return defineComponent(helloWorld, withRequests);

function helloWorld() {
  this.after("initialize", function() {
    this.post(...);
  };
}

Folder Structure

The standard folder structure consists of the following:

• ui — Files that handle DOM interaction
• data — Files that handle data (eg. perform requests, filtering)
• mixins — Mixins, obviously

Event Naming

I recommend using TweetDeck’s guide to event naming in Flight. The three below are the ones I most commonly use:

• UI data request — uiNeedsUsers
• UI request — uiRemoveUser, uiShowUsers
• Data event (usually a flow-on from a UI data request) — dataUserProfile

A quick example of how these could work can be found here.

Smooth Landing

Although Flight is not gaining the same amount of traction as Backbone.js or AngularJS, it is a more than worthy competitor. Although it does not provide Model-view-controller functionality out of the box, the developer has full control over how data will be managed, how rendering will be performed and so on. If you’re interested, head on over to the Flight website and try it out.