feat(*): Prepare release 2.1.0

julienloizelet · Aug 2, 2023 · 1d1d209 · 1d1d209
1 parent 9f259e5
commit 1d1d209
Show file tree

Hide file tree

Showing 2 changed files with 27 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -13,6 +13,17 @@ The public API for this project is defined by the files `docker-compose.playwrig
 ------
 
 
+## [2.1.0](https://github.com/julienloizelet/ddev-playwright/releases/tag/v2.1.0) - 2023-08-02
+[_Compare with previous release_](https://github.com/julienloizelet/ddev-playwright/compare/v2.0.1...v2.1.0)
+
+
+### Changed
+
+- Copies the existing `.ddev/.homeadditions` folder files into `/home/pwuser` during container build so that they are 
+  readable by the `pwuser` that installs playwright ([@see #10](https://github.com/julienloizelet/ddev-playwright/pull/10))
+
+---
+
 ## [2.0.1](https://github.com/julienloizelet/ddev-playwright/releases/tag/v2.0.1) - 2023-07-10
 [_Compare with previous release_](https://github.com/julienloizelet/ddev-playwright/compare/v2.0.0...v2.0.1)
 

diff --git a/README.md b/README.md
@@ -45,7 +45,9 @@ This command will install `playwright` and all dependencies in a folder defined
 
 **Before running this command**, ensure that you have a `package.json` file in the `PLAYWRIGHT_TEST_DIR` folder. You will find an example of such a file in the `tests/project_root/tests/Playwright`folder of this repository. You will also find an example of a `playwright.config.js` file.
 
-By default, `tests/Playwright` is used as `PLAYWRIGHT_TEST_DIR` value, but you can override this value to suit your need by creating a `docker-compose.override.yaml` in the `.ddev`  root directory with the following content: 
+By default, `tests/Playwright` is used as `PLAYWRIGHT_TEST_DIR` value, but you can override this value to suit your 
+need by creating a `docker-compose.override.yaml` (or any `docker-compose.<some-good-name>.yaml` file) in 
+the `.ddev`  root directory with the following content: 
 
 ```yaml
 services:
@@ -54,7 +56,7 @@ services:
       - PLAYWRIGHT_TEST_DIR=your/playwright/directory/path
 ```
 
-You could also edit the value directly in the `docker-compose.playwright.yaml` file but you risk losing your changes every time you do a  `ddev get julienloizelet/ddev-playwright` (unless you delete the `#ddev-generated` line at the beginning of the file).
+You could also edit the value directly in the `docker-compose.playwright.yaml` file, but you risk losing your changes every time you do a  `ddev get julienloizelet/ddev-playwright` (unless you delete the `#ddev-generated` line at the beginning of the file).
 
 In addition, if there is a `.env.example` file in the folder, it will be copied into a `.env` file (to be used with the `dotenv` package for example).
 
@@ -113,9 +115,19 @@ For example:
 
 ## Technical notes
 
-### arm64
+### `arm64`
+
+On `arm64` machine, edit the `playwright-build/Dockerfile` file to use `mcr.microsoft.com/playwright:focal-arm64` base image.
+
+### `.npmrc` file and `.ddev/.homeadditions`
+
+If you wish to use a specific `.npmrc` file (for private NPM registries for example), you just need to place the `.
+npmrc` file in the `.ddev/.homeadditions` folder of your project. This way, the `ddev playwright-install` command 
+will automatically retrieve it.
+
+More generally, all the `.ddev/.homeadditions` folder content is copied to `/home/pwuser` folder when the `playwright` 
+container is build.
 
-On arm64 machine, edit the `playwright-build/Dockerfile` file to use `mcr.microsoft.com/playwright:focal-arm64` base image.
 
 ## Thanks