This PR brings in a new production/public variation of the Docker image for running the browser. This works more-or-less like the last one did in the sense that it supports HTTPS and requires HTTP basic authentication (password protection). However, it follows the workflow of our new container where, the user provides their project directory as input, and the container handles importing and building it before launching an instance of the browser.
For running locally, that workflow has also been improved thanks to a new script, bin/run_project. Now (assuming the image is already built), a user simply runs the script and provides the directory with their project as an argument.
This PR brings in a new production/public variation of the Docker image for running the browser. This works more-or-less like the last one did in the sense that it supports HTTPS and requires HTTP basic authentication (password protection). However, it follows the workflow of our new container where, the user provides their project directory as input, and the container handles importing and building it before launching an instance of the browser.
For running locally, that workflow has also been improved thanks to a new script,
bin/run_project. Now (assuming the image is already built), a user simply runs the script and provides the directory with their project as an argument.