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: DEVELOPMENT.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,24 @@ Individual scripts can be iteratively developed, debugged, and tested using the
15
15
16
16
First, build a baseline of the image to include the packages needed by existing or new scripts:
17
17
18
-
```shell script
19
-
docker build -t mc-dev .
18
+
PowerShell:
19
+
```powershell
20
+
$env:IMAGE_TO_TEST="mc-dev"
21
+
docker build -t $env:IMAGE_TO_TEST .
22
+
pushd tests/setuponlytests/vanillatweaks_file/
23
+
docker-compose run mc
24
+
docker-compose down --remove-orphans
25
+
popd
26
+
```
27
+
28
+
Bash:
29
+
```bash
30
+
export IMAGE_TO_TEST=mc-dev
31
+
docker build -t $IMAGE_TO_TEST.
32
+
pushd tests/setuponlytests/vanillatweaks_file/
33
+
docker-compose run mc
34
+
docker-compose down --remove-orphans
35
+
popd
20
36
```
21
37
22
38
Using the baseline image, an interactive container can be started to iteratively run the scripts to be developed. By attaching the current workspace directory, you can use the local editor of your choice to iteratively modify scripts while using the container to run them.
@@ -116,4 +132,4 @@ for b in "${branches[@]}"; do
116
132
git merge -s ours -m "Track latest from master" master
0 commit comments