See Bitbucket :

spec-sa

sa-server

Why?

At the moment the project is a collection of components that run fine as a development project but experience indicates that bring the parts together on a real platform will reveal much more about how well the components work together. This process will also reveal comprehension errors in the overall scheme. There are going to be a few of those.

Docker Images

sa-server The api server

The api server image is based of a common base image. That image is built on the clojure base image.

See project sbnl-clj-base

Build the server image from an uberjar :

lein uberjar
docker build . -t sa-server:0.0.1

This can then be run from docker as :

docker run -i -t -p3000:3000 sa-server:0.0.1

Minikube

Deploy the server to minikube kubernetes.

Make the namespace if its not there :

kubectl create namespace sa

Then deploy the server code

kubectl create -f sa-server-local.yaml -n sa

Check that virtual box has the service port avaiable through the bridge connector :

Tags: status:ongoing clojure kubernetes minikube

« Reporting Image Version Information Inside Kubernetes A DSL With Instaparse For The Role Based Security Project »