- Presenter - Michael Irwin
- Slides - PDF | Google Drive
Since this was the first meetup for the Docker Blacksburg Meetup, we started from the beginning. What is Docker? What's it trying to accomplish? How are they trying to reach those goals?
After talking about the high-level goals, we dived into the terminal and practiced pulling images, starting containers, exposing ports, and creating new images. We first created an image by using docker commit, but then learned about the more preferred method... using Dockerfiles.
- Presenter - Michael Irwin
- Slides - PDF | Google Drive
Our use case talk tonight was brought to us by Michael Irwin, a developer on CREST (Comprehensive Research Enterprise Systems Team) at Virginia Tech, where they are building research administration applications. He highlighted how the team had the desire to allow acceptance testing to occur on individual feature branches before being merged into the main code branch.
He then talked about the three different phases of their QA environment, the pros and cons of each, and how they ended up where they are using Docker. The final solution ended up with utilizing the jwilder/nginx-proxy image, which allows for easy reverse proxying of containers. This allowed easy isolation of each branch by isolating each application/database pair on a different subdomain.