This repository contains the source for building a Quicklisp based Common Lisp application as a reproducible docker image using source-to-image. This docker image is CentOS based, but the project includes Dockerfile.rhel7 for creating a RHEL based image as well. The resulting images can be run using docker.
To build a simple sample-lisp-app application using standalone S2I and then run the resulting image with docker execute:
```
$ s2i build https://github.com/atgreen/sample-lisp-app atgreen/lisp-10-centos7 sample-lisp-app
$ docker run -p 8080:8080 sample-lisp-app
```
Accessing the application:
Run interactively as above, you can access the sample-lisp-app like so:
$ curl 127.0.0.1:8080
You will likely, however, prefer OpenShift, where applications are created like so:
$ oc new-app atgreen/lisp-10-centos7~git://github.com/atgreen/sample-lisp-app
A swank server is started on port 4005 for every application. With OpenShift, you can forward port 4005 to your local host and then connect to it with SLIME for interactive Emacs based development. Just identify the pod running your container with oc get pods, and then....
oc port-forward sample-lisp-app-1-h5o5f 4005
Follow this up in Emacs with...
M-x slime-connect RET RET
To teach Emacs how to translate filenames between the remote and local machines, you'll need to define slime-filename-translations.
There are a number of excellent screencasts and tutorials on using SLIME on the project web site at https://common-lisp.net/project/slime.
Note that swank, by default, is configured to only listen on the
localhost loopback device. This works well with OpenShift port
forwarding, as above, but if you run this container by hand you will
want to use the docker --net host option to allow for connections to
swank.
To install this image along with sample application template into OpenShift, run the following as the cluster manager:
```
$ oc create -f lisp-image-streams.json -n openshift
$ oc create -f lisp-web-basic-s2i.json -n openshift
```
To set these environment variables, you can place them as a key value pair into a .s2i/environment
file inside your source code repository.
-
APP_SYSTEM_NAME
The name that quicklisp will know this application by.
-
APP_EVAL
SBCL evaluates this lisp form after ql:quickload'ing :$APP_SYSTEM_NAME. For instance: "(webapp:start-webapp)".