In a previous article, we have spoken in length about what a docker compose is, and how it can help us in creating customized image builds. let's talk about how we can also further specify how the images when containerized should behave when struck with a termination, aka their "restart" behavior expectations.
So far we have seen in details about how we can provide Google and Facebook authentication for a user with each provider having its own configuration and middleware invoked. In general scenarios, one would prefer providing multiple options for user to signin as it can open up multiple sections of audience
a docker-compose is a command which comes out of the box along with the docker installation, that helps in keeping instructions to run a container out of an image simple without missing out on any instruction which needs to be passed on while creating a container.
Let's look at a hypothetical scenario, wherein we would want the authentication middleware to completely be bypassed, but yet the user context for the request be setup for us to use at a later point in the request pipeline.
A Dockerfile is a configuration file which describes the docker runtime on how to build a customized image from an existing base image and how to get things started. It is useful in building exportable containers for applications which can later be used in creating and deploying containerized nodes.
To get started in the world of docker way of application deployment, we require to get ourselves familiar with a few commands which do jobs like starting, running and terminating a "container" along with commands which help in monitoring the containers and executing commands over them.