Hi all, I've created a small docker setup that builds and runs CAS in docker using a multi-stage build, resulting image is about 173MB. We're planning on using this to build & run our production CAS servers when we update to 5.1.x. Does this seem reasonable? The github repo is at: https://github.com/crpeck/cas-overlay-docker
The way it works is that the first stage clones the git repo from https://github.com/apereo/cas-overlay-template (branch master), copies in any overlay files, then builds cas.war using mvn clean package. The second stage copies in the warfile from the 1st stage, copies etc/cas into the container and runs java -jar cas.war One thing that would be helpful is if releases to the cas-overlay-template repo were tagged with the version, as in 5.1.3 would have a tag of 5.1.3, 5.1.4 would be tagged 5.1.4, that way when I go production I can clone based on the tag I want. Thanks, Chris Peck -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAFZ1tgYkyvhstENUFTJbTdRN5Dy9xw4BMS_xmQDALK%3DN8QOkhg%40mail.gmail.com.
