This post plans to illustrate how you can build and dockerize and Mojolicious application and solve... Tagged with docker, perl, devops, mojolicious.

Check out this consolidated list of things you can (or should) do when using Docker to run SQL Server on a Mac.

PerlCon 2019 Rīga — Day 1 — 7 August 2019

https://perlcon.eu/talk/27

Some time ago we had the glorious idea to deploy our code into the cloud. The Google cloud, to be specific. This means we had to learn Kubernetes (to manage and scale our apps), Docker (to pack the apps into containers), gitlab CI (to automate the deployment process) and a whole lot more.

In this talk I'll explain the basics of Kubernetes, Docker and CI; describe how to make your app code cloud ready; and show you our current deployment pipeline.

Be prepared to see Perl, YAML, bash, Makefiles and other horrors required for smooth sailing in the clouds.

Step 4. Multistage Build

In our previous configurations, we were copying all of our source codes into the working directory.
But it’s unnecessary as we only need the build folder to serve our website. So now we will use the concept of multi-stage build to cut down the unnecessary code and dependencies from our final image.
The configuration will look something like this.

# STAGE 1

FROM node:12-alpine AS build
WORKDIR /app
COPY package.json ./
RUN yarn  install
COPY . /app
RUN yarn build

# STAGE 2
FROM node:12-alpine
WORKDIR /app
RUN npm install -g webserver.local
COPY --from=build /app/build ./build
EXPOSE 3000
CMD webserver.local -d ./build

Note: Alpine images are already very small and will probably be sufficient if you care about size.

German Perl Workshop 2019 München 2019-03-06
Thomas Klausner

Why use Docker as a developer?

This tool can really change a developer’s daily life. In order to best answer this question, I have written a non-exhaustive list of the benefits you will find:

Docker is fast. Unlike a virtual machine, your application can start in a few seconds and stop just as quickly.
Docker is multi-platform. You can launch your container on any system.
Containers can be built and destroyed faster than a virtual machine.
No more difficulties setting up your working environment. Once your Docker is configured, you will never have to reinstall your dependencies manually again. If you change computers or if an employee joins your company, you only have to give them your configuration.
You keep your work-space clean, as each of your environments will be isolated and you can delete them at any time without impacting the rest.
It will be easier to deploy your project on your server in order to put it online.

Getting Started with Kubernetes sounds like quite a daunting feat. How do you get started with “an open-source system for automating deployment, scaling, and management of containerized applications”?

I love Docker. At first it seemed a bit silly to me for a small-scale implementation like my home setup, but after learning how to use it, I fell in love. The standard features are certainly beneficial. It's great not worrying that one application's dependencies will step on or conflict with another's. But most applications are good about playing well with others, and package management systems keep things in order. So why do I docker run instead of apt-get install? Individualized system settings.