Merge pull request #4 from outofcoffee/feature/apiman-on-wildfly9

Adds Dockerfile for apiman 1.2.1.Final on Wildfly 9

on-wildfly9/Dockerfile

@@ -0,0 +1,12 @@
+# Use Wildfly 9 image as the base
+FROM jboss/wildfly:9.0.2.Final
+
+MAINTAINER Eric Wittmann <[email protected]>
+
+ENV APIMAN_VERSION 1.2.1.Final
+
+RUN cd $HOME/wildfly \
+ && curl http://downloads.jboss.org/apiman/$APIMAN_VERSION/apiman-distro-wildfly9-$APIMAN_VERSION-overlay.zip | bsdtar -xvf-
+
+# Set the default command to run on boot
+CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0", "-c", "standalone-apiman.xml"]

on-wildfly9/README.md

@@ -0,0 +1,41 @@
+apiman on wildfly 9
+===================
+
+## Usage
+
+To start up apiman
+
+    docker run -it apiman/on-wildfly9
+
+You may want to map the port(s) so you can access the app
+
+    docker run -it -p 8080:8080 apiman/on-wildfly9
+
+## Building the image
+
+    docker build -t="apiman/on-wildfly9" --rm .
+
+## Image accessible on Docker hub
+
+This image is automatically built and published into [Docker Hub][apiman_dockerhub].
+
+
+## How to extend the image
+
+You might probably want to extend the image. Usually creating/enabling admin user for wildfly is a good practice, and also, if you want to debug the apiman, you can enable debugging, and expose the debug port like so:
+
+    FROM apiman/on-wildfly9
+    RUN $JBOSS_HOME/bin/add-user.sh admin admin123! --silent
+    EXPOSE 8787
+    CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0", "-c", "standalone-apiman.xml", "--debug"]
+
+You can build your own extended image with:
+
+    docker build --rm -t "myname/apiman-on-wildfly9:latest" .
+
+And then run it like:
+
+    docker run -it --rm -p 8080:8080 -p 9990:9990 -p 8787:8787 myname/apiman-on-wildfly9
+
+
+[apiman_dockerhub]:https://registry.hub.docker.com/u/apiman/on-wildfly9/