Nisarga Patel

Product Management, Software Development, Entrepreneurship, IoT, Crypto

Creating a Barebones Golang Project with Vendoring Via a Custom Setup Script

Often times one may want to create a barebones Go project with dependency vendoring. I recently created a simple script which allows one to quickly scaffold a Go project that uses the vendoring tool govendor.


In order to use the script you must have already installed Go, if you’re on Mac and have Homebrew. You can easily install Go via brew install go. For install directions for other platforms check out the official Go docs. This tutorial is written from the perspective of Mac or Linux.

The barebones project setup script

The project setup script scaffolds out project folders and prompts you to add common dependencies and also has support for adding your own custom dependencies.

You can take a look at the code for the setup shell script here.

How to use it

After you have installed Go, the first step is to get the code for the script via git clone:

git clone

Elsewhere create a new directory for your project

mkdir projectname

Copy over the starter script from the cloned directory into your project directory

cp project-starter-scripts/ projectname/

Change directories to the project directory

cd projectname/

Run the script


Upon running the script you will be prompted for the name of your username or organization, and the name of your project.

Here is an example:

Welcome to the Golang project starter
Enter the GitHub organization or username: YOURUSERNAME
Enter the name of your project repo: YOURPROJECTNAME
Setting up directories...
Brought in govender and installed dependencies via ...
Common dependencies...
Do you want gin-gonic? (y/n):

Next you will be prompted if you’d like certain common dependencies in your project

Do you want gin-gonic? (y/n): n
Do you want mgo (mongo driver)? (y/n): n
Do you want pq (postgres driver)? (y/n): n
Do you want mysql (mysql driver)? (y/n): n
Do you want gocql (apache cassandra driver)? (y/n): n
Do you want go-redis (redis driver)? (y/n): n
Do you want gin-jwt? (y/n): n
Do you want jwt-go? (y/n): n
Do you want protoc-gen-go (protocol buffers for gRPC)? (y/n): y
Do you want any custom dependencies? (y/n): y
Whats the url for your custom dep:
Do you want any custom dependencies? (y/n): n
Run source to set your GOPATH and GOBIN.

At the end you’ll be prompted for any custom dependencies which you can specify. It will keep on prompting you for custom dependencies until you type n.

At this point your barebones Go project should be all setup for development. In order for your files to notice the dependencies you have to specify the GOPATH and GOBIN environment variables. The setup script creates a file which does this for you if you run source, you can also optionally create an alias in your bash configuration that sets those path variables.

You can look at the value of your GOPATH and GOBIN variables by running:

echo $GOBIN && echo $GOPATH
Creating a Go file and testing out a dependency

After ensuring that your GOPATH and GOBIN variables are set to your root project directory you can now test out a dependency by creating a Go file.

In your project directory

cd src/

And create a file called main.go. Here is a sample Go file that uses the custom zap logger dependency added:

package main

import (

func main() {
	logger, _ := zap.NewProduction()
	defer logger.Sync()
	logger.Info("Testing the logger",
		zap.String("Some String", "An important string"),
		zap.Int("Some Integer", 5),
		zap.Duration("Some Duration", time.Second),

As long as your GOPATH and GOBIN variables are set correctly to the project root running go run main.go should give you the following output:

> go run main.go
{"level":"info","ts":1528577748.722416,"caller":"YOURPROJECTNAME/main.go:11","msg":"Testing the logger","Some String":"An important string","Some Integer":5,"Some Duration":1}
Setting GOPATH and GOBIN via a bash alias

Here’s the alias for quickly setting the GOPATH and GOBIN environment variable if you choose not to use the source method:

alias gp='GOPATH=`pwd`; export GOPATH; GOBIN=$GOPATH/bin; export GOBIN'

Usually you can add the alias in the ~/.bashrc or ~/.bash_profile file, you can find out what the bash configuration file is for your particular OS.


I often create a Makefile as well for larger projects which has support for cross platform compilation:

	GOOS=linux GOARCH=amd64 go build -o bin/programname-linux-amd64 src/*.go
	cp config.json bin/config.json
	GOOS=darwin GOARCH=amd64 go build -o bin/programname-mac-os-amd64 src/*.go 
	cp config.json bin/config.json
	GOOS=linux GOARCH=arm go build -o bin/programname-linux-arm src/*.go 
	rm -r bin/*

Using this Makefile it becomes easy to compile for different platforms by doing:

make all_linux
make all_mac_os
make all_arm

I would also have a Makefile command for running tests as well.


I hope you enjoyed this post on setting up a barebones Go project with vendoring via a setup script. If you have any suggestions, edits, or comments feel free to comment down below.


comments powered by Disqus