6 Commits (e1166b5ebdbbfb184dfd482227d11a28f33f40c9)

Author	SHA1	Message	Date
Jesse Vincent	4c421277a7	make a comment in run-docker shellcheck friendlier	4 years ago
Jesse Vincent	b70b851321	Teach docker-run to run interactively or to be able to run from a non-interactive process like a git hook ... Fixes #959	4 years ago
Michael Richters	26f4ef498a	Set BOARD_HARDWARE_PATH correctly for run-docker on macOS ... Because ARDUINO_LOCAL_LIB_PATH was being set to a default value for other operating systems before checking the OS version, it would never get set correctly for macOS (unless it was already set externally). This change fixes that problem so that it's no longer necessary to set BOARD_HARDWARE_PATH externally when executing `run-docker`. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Gergely Nagy	ba7b496af5	Rework our Docker config for performance ... * never try to write anything to the host's disks * read as little as possible from the host's disks * keep source in ram * cache build artifacts and intermediate content persistently Most of these hacks are only necessary because Docker disk performance on macOS is...not performant Signed-off-by: Jesse Vincent <jesse@keyboard.io> Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago
Gergely Nagy	0f7ff140fc	docker: Simplify the Dockerfile a little ... We can pass arguments to the entrypoint from the `docker run` commandline, so we do not need to do that via an environment variable. This way, we're an environment variable and an `eval` shorter. Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago
Gergely Nagy	c743befb7f	Add a small tool, to run things within Docker ... To make it easier to reproduce things, and to help build in a clean environment, this adds a thin Dockerfile that has Arduino and arduino-cli pre-installed, and - along with the `bin/run-docker` script - is set up so that one can easily run arbitrary commands in the context of the current bundle and Kaleidoscope. The first run will take a while, because docker will build the image. Subsequent runs will use the cache. To use: `bin/run-docker make`, for example. Any argument passed to the `bin/run-docker` will be eval-ed within the container, and will run there. Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago