How to show test tasks on the developer's backend?

Question

Software Deployment

There is a test task to write something using Laravel, I have a VDS on which I can install everything I need. Let's say I need php 7.2, Postgres, Redis, ElasticSearch. I can do the task directly on VDS, I can do it on Vagrante (on a Windows 7 home machine).
The employer asks first to put the code on GitHub, everything is clear with this, and also asks to describe how to deploy the project. Do not show the test task from my VDS?
A good option would be Docker, which I have not worked with yet, because there are a lot of problems with it on Windows. At the same time, I would also learn the basic knowledge of Docker (and demonstrate), which would be a plus.
I do not want to install Linux as a second system. I do simple projects that require Php, mysql and Apache on OpenServer under Windows. Nginx + PHP-FPM + Redis plus something else I can on Vagrant, but it's heavy.
Maybe it’s better to put Linux on a virtual machine, learn how to do everything on Docker in it, and already throw off the docker with my test task to the employer, because some bearded team leader probably has Linux, well, or a Mac?
How to be?

Answer 1

Good afternoon!
I doubt that it is so necessary to master a new technology for a test task - show what you already know, your VDS is excellent. The employer usually cares that you have encountered this and have already figured it out, you do not have to delve into it from scratch. Don't be shy about not knowing some of the technologies, show your intent to learn and you'll be fine.
As for Docker, it's easier to understand when you have experience (configuration + software installation) on the command line of some UNIX/Linux system. In fact, to deploy the environment, you need to do several things:
1) Install docker,
2) Download some basic container image (there is, for example, an ubuntu-based container that already has apache + php 7.2 installed)
3) Make a Dockerfile for this image, in which you can write commands for installing additional required software
4) Configure docker so that a folder on your hard drive of your choice is displayed in the container file system - for example, you can add static content there
5) Configure the necessary software
6 ) Upload data and start using)
Large +++++ - once compiled Dockerfile will allow you to add containers with the same software indefinitely)