You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guide/README.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,15 +48,12 @@ That said, unless you have a specific reason, it’s recommended to use `localde
48
48
49
49
## ➕ Adding Dependencies
50
50
51
-
When introducing new dependencies, make sure to update both the **local development environment** and the **CI build environment**, as they are managed
52
-
separately.
51
+
### 🐍 Python Packages
53
52
54
-
### 💻 Locally
55
-
56
-
To update the local environment, open the `Dockerfile` and modify the `RUN pip install ...` line to include any additional packages you need.
53
+
Python dependencies are declared in `requirements/requirements.in`.
54
+
After editing this file to include the new packages, run the `requirements/requirements.sh` script.
55
+
This will regenerate `requirements/requirements.txt`, which is the file actually used by both the localdev and CI environments to install dependencies in a consistent and reproducible way.
57
56
58
-
### 🤖 In CI
57
+
### 🐧 Alpine Linux Packages
59
58
60
-
Dependencies for the CI environment are declared in `requirements/requirements.in`.
61
-
After editing this file to include the new packages, run the `requirements/requirements.sh` script.
62
-
This will regenerate `requirements/requirements.txt`, which is the file actually used by the CI to install dependencies in a consistent and reproducible way.
59
+
To add Alpine system packages, modify the `Dockerfile` directly.
0 commit comments