Running the app in Docker Case Study
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Running the app in Docker Case Study
Overview
A junior developer has asked you to help him Dockerize an application so that his buddies can work on it locally. The app is a part of a secret project and he can’t tell you what it does, other than that it’s a web app configurable via environment variables, and it has a dependency on Redis. Also, the app currently has a bug where “it stops working” after “a little while.” He’s super sorry about that and he promises that it will be fixed in the next sprint… if you can help him figure out what’s wrong with it. Are you a bad enough dude to help out this poor engineer?
Instructions
- Run the Dockerized app yourself (including Redis). If you have to make any changes to the Dockerfile so that the application starts properly, send us your edited Dockerfile, along with any other configuration files you create to get it working. Briefly explain to us (as the junior developer) what your fixes are and how to run everything.
- Send a screenshot of the a valid, non-error (ie, HTTP 200 status code) result of the web app running in the docker container.
- What can you tell the developer that might help him address any bugs in the upcoming sprint?
Basic Requirements
Running the app in Docker Case Study
- All documentation should be in Markdown format.
- Run the app in Docker. Feel free to use the full suite of Docker tools (DAB, Compose, Swarm, etc.)
- Reproduce the behavior the developer describes as “it stops working.”
- Describe any failures you observe and indicate where (in code) the developer should focus when fixing those failures.
Bonus Points
- The developer snuck a FizzBuzz implementation into the code, but there’s a bug in it. What’s the bug and what does he need to change to fix it?
- Can you make this app’s Docker image any smaller?
- Write an application that successfully implements FizzBuzz in a language of your choice.
Dockerfile
Copy and paste the text below into your dockerfile.
FROM alpine:latest RUN apk update && apk add wget ca-certificates && \ cd /sbin && wget https://s3.amazonaws.com/ml-sreracha/sreracha RUN adduser -S -H -s /bin/sh www EXPOSE 80 USER www ENTRYPOINT /sbin/sreracha
RUBRIC
Excellent Quality
95-100%
Introduction 45-41 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Literature Support
91-84 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Methodology
58-53 points
Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met.
Average Score
50-85%
40-38 points
More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided.
83-76 points
Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration.
52-49 points
Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met.
Poor Quality
0-45%
37-1 points
The background and/or significance are missing. No search history information is provided.
75-1 points
Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration.
48-1 points
There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow Running the app in Docker Case Study