Loading…

Wrap-up and resources

Key Takeaways

1. Docker: images, containers and volumes: An image is a fixed recipe; a container is a running copy you can throw away. What must last (the database) lives in a volume, not inside the container.
2. Environments, configuration and secrets: The code is one; the settings come from the environment. Validate them all at startup and fail clearly, and never commit a secret to the repository.
3. Deploying to the cloud: Start with the simplest hosting that is enough. Deploy the same tested image, add a health check, run migrations before the new release, and know how to roll back before you need to.

Term	Definition	Part
Image	A read-only template built from a Dockerfile.	1
Container	A running copy of an image, deleted and recreated.	1
Volume	Lasting storage outside the container.	1
Environment variable	A value the program reads from the system it runs on.	2
.env.example	Documents setting names with dummy values in the repository.	2
Fail fast	Failing at once on startup if something is missing.	2
PaaS	A platform that runs servers for you: push and it runs.	3
Health check	A route the platform asks to know whether the version is healthy.	3
Blue/green	Two full copies, switching traffic between them at once.	3

Grouped by type. Start with the official docs for precision, or an article or video for the explanation.