Originally posted by microrache January 3, 2022
It would be cool to have something like a "public"- or "assets"-folder which is exposed by Verdaccio's web server. This folder then could be mounted as a Docker Volume, where e.g. screenshots and other assets are stored. These assets then could be referenced in the package's README.md like 
It already worked in the described way in Verdaccio 4.x by mounting a Docker Volume to: /opt/verdaccio/node_modules/@verdaccio/ui-theme/static/screenshots
But since v5 there seems to be no static-folder or anything comprehensible, which can be used for the desired purpose. Is it possible to re-implement such a directory?
What to consider
This might be a plugin (middleware)
Docker needs to be aware of this assets folder
Any security implication? 🤔
The text was updated successfully, but these errors were encountered:
Discussed in #2853
Originally posted by microrache January 3, 2022
It would be cool to have something like a "public"- or "assets"-folder which is exposed by Verdaccio's web server. This folder then could be mounted as a Docker Volume, where e.g. screenshots and other assets are stored. These assets then could be referenced in the package's README.md like
It already worked in the described way in Verdaccio 4.x by mounting a Docker Volume to:
/opt/verdaccio/node_modules/@verdaccio/ui-theme/static/screenshotsBut since v5 there seems to be no static-folder or anything comprehensible, which can be used for the desired purpose. Is it possible to re-implement such a directory?
What to consider
The text was updated successfully, but these errors were encountered: