Hi @Biont,

Thanks for the PR.

Is there any reason not to use a volume for such a purpose?

Something like the following in a docker-compose.override.yaml is not working ? :

services:
  playwright:
    volumes:
      - /some/path/on/your/host/to/.npmrc:/home/pwuser/.npmrc

Yes I think this is something I should explore first. Frankly, I now wonder why this didn't occur to me before I considered the entrypoint script.

@julienloizelet I thought about this some more.

I do think there's value in making the container behave similar to the main DDEV web container.
Also, we already have the files present within the container, so why shouldn't we just use them to faciliate this kind of setup. Requiring an external mount introduces some maintenance effort for every project that uses this addon - for something that could be working out of the box (with files that already exist, just in an inconvenient place)

DDEV itself actually just grabs the entire folder and copies it into the local home directory
Would this be something we could just mimick here? It would allow even more tools to "just work"

@Biont ,

I am already using a docker-compose.override.yaml to override the PLAYWRIGHT_TEST_DIR variable.

services:
  playwright:
    environment:
      - PLAYWRIGHT_TEST_DIR=your/playwright/directory/path

That's why I was suggesting to do the same to handle project specificity.

But why not, do you mean we could copy the entire .homeadditions folder in /home/pwuser ?

Just a note that docker-compose.override.yaml naming doesn't have any value that I know of. Just docker-compose.<somegoodname>.yaml is all you need.

@julienloizelet I updated the PR so it sets up the entire homeadditions folder.

@rfay thanks for stopping by. While I have your attention, do you see any downsides to this approach?

If you're asking whether you can copy ~/.ddev/homeadditions into a separate container, I know of no reason that should be a problem; it will be best if the container is Debian/Ubuntu.

Merged.

I guess I will add something in the README (maybe just to explain how to use a .npmrc file) before publishing a release.

Thanks again.