What:
Move saving and loading images to separate class/module

Why:
If this logic will be described in separate entity, it will be easier to read code and will help to avoid code duplication.

How:
Probably, this entity will have two functions:

• save image with given name (and create *.SUCCESS file to flag that file saved)
• load image with given name (if flag file *.SUCCESS exists, otherwise - return message that message doesnt exist by now)

What:
Add full information about how to use this instrument to README.MD.

Why:
Users cannot try this instrument without reading the code - this is too complicated.

How:
Should be described:

• every entity of type action
• endpoints
• also, examples could be good

What:
Remove poetry from Dockerfile.

Why:
Docker image should be as tiny as possible

How:
Using Poetry we can build wheel or sdist and install it into image.

Why:
Chrome don't want to start when user is root. It wants --no-sandbox parameter.

What:
Need to make chrome start correctly.

How:
Run it with --no-sandbox
OR
Change user in container from root to someone else.

Background

It was discovered that there are some hard coded values, like path to folder where images shall be saved to or path to the directory for logs.

Problem

These hardcoded values prevents project from being used by a broader community.

What to do

Make the application configurable.

Definition of done

There are no hardcoded values in the code base of the project.

What:
Implement saving more than one screenshot - for each “make_screenshot” action.

Why:
Because rewriting screenshot on each action is incorrect and inefficient behavior.

How:
If there is more than one action of making screenshot, app should save it like img_id.png, img_id_1.png, img_id_2.png... img_id_N.png. Also, downloading of screenshots should return all of them.

Why:

To deploy easily we need dockerfile with fully configured service

What:

Need to write dockerfile and edit compose, if needed

Why:

For more info while debugging

What:

Write logger factory so each module could generate its own logger