Change Details

The Docker setup for WVUI has room for some improvements: [] The release scripts to easily release a new version of WVUI on npm. Those scripts as of now can only be run outside the container, but ideally should be run inside Docker with a command like: `docker-compose run --rm node ./bin/release-dev`. [] Based on your host OS, the Dockerfile will behave differently in assigning Docker generated files a user and group. The docker-compose commands also require build arguments (docker-compose run --rm --build-args UID) to get this to work properly. Look into a cleaner way of doing this, to be consistent across OS's and/or remove the number of CLI args required.

The Docker setup for WVUI has room for some improvements: [] The release scripts to easily release a new version of WVUI on npm. Those scripts as of now can only be run outside the container, but ideally should be run inside Docker with a command like: `docker-compose run --rm node ./bin/release-dev`. Another option: move the `prepublishOnly` NPM script out of package.json and into the shell scripts, and call `docker-compose run --rm node <command>` from the shell scripts as needed. [] Based on your host OS, the Dockerfile will behave differently in assigning Docker generated files a user and group. The docker-compose commands also require build arguments (docker-compose run --rm --build-args UID) to get this to work properly. Look into a cleaner way of doing this, to be consistent across OS's and/or remove the number of CLI args required.

The Docker setup for WVUI has room for some improvements: [] The release scripts to easily release a new version of WVUI on npm. Those scripts as of now can only be run outside the container, but ideally should be run inside Docker with a command like: `docker-compose run --rm node ./bin/release-dev`. Another option: move the `prepublishOnly` NPM script out of package.json and into the shell scripts, and call `docker-compose run --rm node <command>` from the shell scripts as needed. [] Based on your host OS, the Dockerfile will behave differently in assigning Docker generated files a user and group. The docker-compose commands also require build arguments (docker-compose run --rm --build-args UID) to get this to work properly. Look into a cleaner way of doing this, to be consistent across OS's and/or remove the number of CLI args required.