Getting started with Wercker and Go

This guide is a step-by-step approach to developing, building and deploying a sample app with Wercker within minutes.

While this guide uses Go, the general concepts explained in this tutorial apply to every other programming language.

Requirements

To be able to follow along with this guide, you will need the following things:

  • A Wercker account
  • The Wercker CLI

Setting up the app

Before we can start developing, we have to fork and clone the sample app into our local development environment. After you’ve done that, cd into the project directory:

$ cd getting-started-golang/

Next, build and run the app to verify everything is working:

$ go build
$ ./getting-started-golang

Now in your browser navigate to localhost:5000/cities.json and you should be presented with the following json:

{"cities":["Amsterdam","Berlin","New York","San Francisco","Tokyo"]}

Developing the app

Now that we’ve setup our app we can start developing. Our list of cities is a bit short, so why not add another one in there? Before we do that however, let’s first take a look at the wercker.yml file included in your project folder.

wercker.yml

The wercker.yml is the only config file you need for using wercker. In it, you will define all your steps needed to successfully develop, build and deploy your application. To get started, we’re only interested in developing our app. Take a closer look at the top of the file:

# The container definition we want to use for developing our app
box:
  id: golang
  ports:
    - "5000"

This initial box section defines two things. The id property states which container image you want to use for your project; as we’re developing with Go in this sample we’re using the default golang image. These container images are retrieved from Docker Hub if no other registry is specified. You can read more about containers here. The ports property specifies the ports that you want your running container to expose. This example only requires a single port but you can specify multiple ports here.

Now let’s look at the dev section:

# Defining the dev pipeline
dev:
  steps:
    - internal/watch:
        code: |
          go build ./...
          ./source
        reload: true

In the dev pipeline clause we define what we want to happen in our development pipeline, which in this case is just one step: internal/watch. The internal/watch step watches your files for changes, and if reload is set to true it restarts your app so your changes are reflected immediately. This is especially useful for when you’re developing webapps, as we’re doing now. This step and others are pre-written bash scripts written by either wercker or the community. You can read more about steps here.

Let’s see these steps in action now and fire up our dev pipeline.

Wercker dev

In your project folder, run wercker dev –expose-ports. You should see something similar to the following output:

--> Executing pipeline
--> Running step: setup environment
Pulling repository golang
Pulling image (latest) from golang: ebd45caf377c
Pulling image (latest) from golang, endpoint: https://registry-1.docker.io/v1/: ebd45caf377c
Pulling dependent layers: ebd45caf377c
Download complete: 64e5325c0d9d
Download complete: bf84c1d84a8f
Download complete: 87de57de6955
Download complete: 6a974bea7c0d
Download complete: 3d0d66dec985
Download complete: ec367bd67c88
Download complete: 2d87eca0ec9c
Download complete: ac13965af848
Download complete: 14182e587f2c
Download complete: 37e56f6d02a4
Download complete: 1c18d4d04737
Download complete: 66bf953cd51b
Download complete: 0dfa22e2b56d
Download complete: ebd45caf377c
Download complete: ebd45caf377c
Status: Image is up to date for golang:latest
--> Running step: wercker-init
--> Running step: watch
--> Reloading on file changes
--> Reloading

Wercker first checks out your code and then sets up the container environment. This means that the container will be pulled from Docker Hub and subsequently started with access to your checked out code. It will then start executing all the steps that are defined in the wercker.yml.

If you navigate once again to localhost:5000/cities.json you should see the same output as before. That’s not very exciting, so let’s see our live reloading in action. In main.go:15 add a new city to the array:

Cities: []string{"Amsterdam","Berlin","New York","San Francisco","Tokyo","London"}}

Once you save your changes, the app should automatically reload. If you refresh your page, our new city should be there! Hurrah!

There are many more steps to use for developing your app. Take a look around, and if you can’t find the step you’re looking for, you can always make your own.

Now that we’re done developing, we want to push our changes and let wercker build and deploy our app for us.

Building your app

First, let’s revisit our wercker.yml again.

# The container definition we want to use for developing our app
box:
  id: golang
  ports:
    - "5000"

# Defining the dev pipeline
dev:
  steps:
    - internal/watch:
        code: |
          go build ./...
          ./source
        reload: true

build:
  steps:
    - wercker/golint
    - script:
        name: go build
        code: |
          go build ./...
    - script:
        name: go test
        code: |
          go test ./...

###Build Pipeline

We’re now interested in what’s happening the build pipeline. We’ve added several new steps, to begin with the wercker/golint step. This step checks our code and fails if it thinks we’re not doing a good job. We’ve also added a new kind of step: a script step. This script step is a piece of inline bash code which we’re using to run our tests. You can create and share these kind of steps with the community by submitting a step to our repository. The rest of the steps should be self-explanatory: one for building and for testing.

Wercker build

Now that we have a better understanding of our wercker.yml let’s go ahead and let wercker build our project. In your project folder, run:

$ wercker build
--> Executing pipeline
--> Running step: setup environment
Pulling repository golang
Pulling image (latest) from golang: ebd45caf377c
Pulling image (latest) from golang, endpoint: https://registry-1.docker.io/v1/: ebd45caf377c
Pulling dependent layers: ebd45caf377c
Download complete: 64e5325c0d9d
Download complete: bf84c1d84a8f
Download complete: 87de57de6955
Download complete: 6a974bea7c0d
Download complete: 3d0d66dec985
Download complete: ec367bd67c88
Download complete: 2d87eca0ec9c
Download complete: ac13965af848
Download complete: 14182e587f2c
Download complete: 37e56f6d02a4
Download complete: 1c18d4d04737
Download complete: 66bf953cd51b
Download complete: 0dfa22e2b56d
Download complete: ebd45caf377c
Download complete: ebd45caf377c
Status: Image is up to date for golang:latest
--> Running step: wercker-init
--> Running step: golint
main.go:9:1: exported function CityHandler should have comment or be unexported
--> Running step: go build
--> Running step: go test
ok      _/pipeline/source    0.006s
--> Steps passed
--> Pipeline finished
Success!

Building locally is very useful when you’re not sure your code will run because of some changes you made. As such you don’t want to push these changes to your Git provider just yet.

But since we’ve verified that our app is compiling and running correctly, it’s time to let wercker build & deploy your app in the cloud, which is what we’ll be doing in the next section.

Adding your app to Wercker

The next step is to create a new application on wercker. Head over to https://app.wercker.com/ and select Add application from the top menu bar.

###Select the Owner and Git Provider

First we have to choose who owns the app. For this tutorial, go ahead and select yourself. If you prefer, you can select an organization you created on wercker.

Now select GitHub as your Git provider (BitBucket and GitLab are also available), and then click Next.

###Select the repository

You now see a list of your existing repositories. Select the go-lang example you forked earlier from the list and click Next.

Configure Access

The next step is about configuring access, and the first option wercker will check out the code without using an SSH key is fine for the purpose of this tutorial, because it’s an open source and public application. So go ahead and click Next.

Review application details

Finally, once you’ve verified all the settings, click Create to complete setting up our app. Now you can trigger the first build!

Triggering your first build

The Nicely Done! screen gives you the option to generate a wercker.yml file. But as the repository already contains one, all you have to do is click trigger a build now .

The Runs page now shows a new build has been triggered! This build will do the exact same as the one you triggered locally but now everyone in your team can see and comment on the build.

Wrapping up

Congratulations! You’ve built your first app using Wercker.