chore: add aboutme package

Author: technosophos

Makefile

@@ -2,7 +2,7 @@
 # Some uses for short name:
 # - Docker image name
 # - Kubernetes service, rc, pod, secret, volume names
-SHORT_NAME := example
+SHORT_NAME := pkg
 
 # Enable vendor/ directory support.
 export GO15VENDOREXPERIMENT=1
@@ -14,55 +14,14 @@ VERSION := 0.0.1-$(shell date "+%Y%m%d%H%M%S")
 # Common flags passed into Go's linker.
 LDFLAGS := "-s -X main.version=${VERSION}"
 
-# Docker Root FS
-BINDIR := ./rootfs
+all: build test
 
-# Legacy support for DEV_REGISTRY, plus new support for DEIS_REGISTRY.
-DEV_REGISTRY ?= $(eval docker-machine ip deis):5000
-DEIS_REGISTY ?= ${DEV_REGISTRY}
-
-# Kubernetes-specific information for RC, Service, and Image.
-RC := manifests/deis-${SHORT_NAME}-rc.yaml
-SVC := manifests/deis-${SHORT_NAME}-service.yaml
-IMAGE := ${DEIS_REGISTRY}/deis/${SHORT_NAME}:${VERSION}
-
-all:
-	@echo "Use a Makefile to control top-level building of the project."
-
-# This illustrates a two-stage Docker build. docker-compile runs inside of
-# the Docker environment. Other alternatives are cross-compiling, doing
-# the build as a `docker build`.
+# This builds .a files, which will be placed in $GOPATH/pkg
 build:
-	mkdir -p ${BINDIR}/bin
-	docker run --rm -v ${PWD}:/app -w /app golang:1.5.1 make docker-compile
-
-# For cases where build is run inside of a container.
-docker-compile:
-	go build -o ${BINDIR}/bin/boot -a -installsuffix cgo -ldflags ${LDFLAGS} boot.go
-
-# For cases where we're building from local
-# We also alter the RC file to set the image name.
-docker-build:
-	docker build --rm -t ${IMAGE} rootfs
-	perl -pi -e "s|[a-z0-9.:]+\/deis\/${SHORT_NAME}:[0-9a-z-.]+|${IMAGE}|g" ${RC}
-
-# Push to a registry that Kubernetes can access.
-docker-push:
-	docker push ${IMAGE}
-
-# Deploy is a Kubernetes-oriented target
-deploy: kube-service kube-rc
-
-# Some things, like services, have to be deployed before pods. This is an
-# example target. Others could perhaps include kube-secret, kube-volume, etc.
-kube-service:
-	kubectl create -f ${SVC}
+	go build ./...
 
-# When possible, we deploy with RCs.
-kube-rc:
-	kubectl create -f ${RC}
+test:
+	go test $(shell glide nv)
 
-kube-clean:
-	kubectl delete rc deis-example
 
-.PHONY: all build docker-compile kube-up kube-down deploy
+.PHONY: all build test

README.md

@@ -1,61 +1,15 @@
-# Prototype Component Repo
+# Deis Pkg
 
-This repo is a prototype for what a Deis component's Git repository
-should look like.
+The Deis Pkg project contains shared Go libraries that are used by
+several Deis projects.
 
-A Deis component is...
+## Usage
 
-- An isolated piece of functionality (e.g. a microservice)
-- That can be packaged into a container (via `docker build`)
-- And can be run inside of Kubernetes
-
-Typically, Deis components are written in Go.
-
-## Practical Usage
-
-If you want to experiment with creating a new repo using this framework,
-try something like this:
+Add this project to your `vendor/` directory using Godeps or
+[glide](https://github.com/Masterminds/glide):
 
 ```
-$ mkdir my_project
-$ cd my_project
-$ curl -fsSL https://github.com/technosophos/prototype-repo/archive/master.tar.gz | tar -zxv --strip-components 1
+$ glide get --import github.com/deis/pkg
 ```
 
-## First-Class Kubernetes
-
-Every component must define the appropriate Kubernetes files.
-Preferably, components should use *Replication Controllers* over pods,
-and use *Services* for autodiscovery.
-
-*Labels* should be used for versioning components and also for
-identifying components as part of Deis.
-
-*Secrets* should be used for storing small bits of shared information,
-and their contents may be set at startup time.
-
-All Kubernetes definitions should be placed in the `manifests/` directory.
-
-The _Makefile_ should have targets that use `kubectl` to load
-definitions into Kubernetes.
-
-## Dockerfiles are for Running
-
-Source code should be built either outside of Docker or in a special
-Docker build phase.
-
-A separate Dockerfile should be used for building the image. That
-Dockerfile should always be placed inside of the `rootfs` directory, and
-should manage the final image size appropriately.
-
-(See the Makefile for one possible way of doing a Docker build phase)
-
-## RootFS
-
-All files that are to be packaged into the container should be written
-to the `rootfs/` folder.
-
-## Extended Testing
-
-Along with unit tests, Deis values functional and integration testing.
-These tests should go in the `_tests` folder.
+(The `--import` flag will get any additional dependencies.)

aboutme/aboutme.go

@@ -16,7 +16,7 @@ import (
 	"os"
 	"strings"
 
-	"github.com/deis/deis/pkg/k8s"
+	"github.com/deis/pkg/k8s"
 
 	"k8s.io/kubernetes/pkg/api"
 	"k8s.io/kubernetes/pkg/client/unversioned"