Cleaning Up Your Python Environment Superfund Site
summary
Containerization isolates an application from a messy local Python install by building a reproducible stack: a Dockerfile-built app image, a pulled postgres image for a real database, a parallel unit tests service that runs pytest against the same mounted code, and a lightweight toolkit container for debugging and pinging service names. A crypto trading bot repo (FreeTrade) gains a docker-compose that starts services, runs migrations up/down, exposes ports for GUIs, and makes CI and onboarding reliably fast and portable.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:43Python environment cleanup
- 1:49Containerization layers
- 3:44Docker Compose setup
- 7:04Testing service with Docker
- 9:15Built vs pulled images
- 11:41Alpine images debugging
- 14:12Reproducible environments
- 17:00Integration testing
- 18:25Dockerfile layer caching
- 20:14Database migrations
- 21:15Q&A
related talks
34mModern development environments for Pythonistas
30mHow to Create a Great Local Python Development Environment with Docker
40mDocker and Python: making them play nicely and securely for Data Science and ML
28mDocker-Composing Your Way to a Better Development Environment
28mTesting Complex Python Dependencies With Docker Containers
26mHow to containerize Python applications with Docker
01h 02mDocker for Data Science: Reproducibility and Deployment
30mPython Containers: Best Practices