Marco Verleun
d01a483c4e
Some checks failed
Gitea Actions Demo Training / Explore-Gitea-Actions (push) Failing after 11s
35 lines
861 B
Markdown
35 lines
861 B
Markdown
# From code to production
|
|
|
|
It starts with the code...
|
|
|
|
--
|
|
|
|
Which gets deployed inside/on:
|
|
|
|
- An appliance
|
|
- A host
|
|
- A container
|
|
|
|
Or is reused as an module.
|
|
|
|
---
|
|
|
|
## A (random) app step by step: worker.py
|
|
|
|
Let's explore what happens to an app (written by Jerome Petazzo) which will run inside a container.
|
|
The source code can be found here: [worker.py](https://github.com/jpetazzo/container.training/blob/main/dockercoins/worker/worker.py)
|
|
|
|
We'll see that the number of CVE's will increase as the code moves on during the build process from app to container image.
|
|
|
|
We will not focus on the application logic, only on the safety.
|
|
|
|
We want to assure our customers/users/ops collegues that the code does not contain any critical CVE's.
|
|
|
|
How can we do this?
|
|
|
|
---
|
|
|
|
## How is this done in the food industry?
|
|
|
|
Let's first look at how the food industry is doing this.
|