How to solve the problem using Docker?

M

mozzart_live2020-09-23 10:48:16

LAMP

mozzart_live, 2020-09-23 10:48:16

Hi all!

I want to note right away that Docker is on you, but I really want to figure it out and solve this problem.

We have a web application (nginx + php-fpm + mysql), we need to give potential buyers the opportunity to feel the application, while with the ability to "break" (modify) it, access is limited - we do not give source code.
You need a tool that will allow you to easily deploy the test bench, then kill it and re-deploy it.
An important point - on one machine, I want to deploy an unlimited (within reasonable limits) number of containers with test benches.

I would be grateful for links, developments, tips on architecture.

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

D

Dmitry, 2020-09-23
@mozzart_live

So expand, what the question is not clear.
If the machine is under your control, if your containers are deployed from your private registry (the place where the prepared containers are stored), then you can make as many stands as you like and run and kill them as much as you like and the code will not get to the client.
if you really want to do it in a fashionable youth way - master Terraform to manage the docker - you can deploy your code with a slight movement of your heel, at least to a test bench to show the client, at least to Amazon, so that everything starts spinning at once ..

S

Sanes, 2020-09-23
@Sanes

You can deploy a test bench from a backup. Let them touch, break. Through the scheduler, we simply deploy the backup. Docker is completely useless here.
Ansible scripts for the environment and management are written in 1 day. Example