Releases: binci/binci
Minor: Fix Windows temp pathing issues
5.8.0 5.8.0
Minor: Output when service images are pulled
Shows a message to indicate when a service image is not local, indicating that it will be pulled during startup.
Patch: Lowercase dockerfile builds
5.6.1 5.6.1
Allows Setting User
The configuration (binci.yml) now support the following syntax for setting the USER on primary and service containers:
user: username # specific usernameuser: 1000 # specific UIDuser: ${UID} # UID or other environment variableRelative volume mounts
It is now possible to mount host folders using a relative path!
volumes:
- ../my-module:/app/node_modules/my-moduleWhile there are many great reasons to use this feature, a common use case is in mounting dependencies from their own project folders directly into an application that uses it. While this was possible before with an absolute path or a path using ${HOME}, now it doesn't matter if everyone on your team uses a different folder structure as long as the projects are in the same relative place.
Cached project folder mount
Recent versions of Docker for Mac support cached volume mounting for wildly reduced filesystem I/O time. Binci 5.4.0 now uses cached mode automatically when mounting the local project folder. Volumes specified in the binci.yml can, as always, include the new :cached or :delegated directives at the end of the path in the same way they would be used on the CLI at the user's discretion.
Rebuild on Change
For those who have Binci set to build containers from a Dockerfile, changes to the Dockerfile have always triggered a rebuild. But what about files like dependency lists that can change what goes into your built image without altering the Dockerfile? You end up running your code on the same old container without the new dependencies, and errors abound.
Today's release fixes that with the rebuildOnChange key. Simply specify a list of files that should cause a rebuild the new time a binci task is run if they get changed:
dockerfile: ./Dockerfile
rebuildOnChange:
- requirements.txtNow, when requirements.txt is updated either by you or by a git pull, the next binci task you run will rebuild your container first.
Image tags
Binci can now automatically tag images that it builds from a Dockerfile. This allows images to be immediately run, pushed, extended, or reused after a binci command causes it to be built, without requiring a rebuild.
Patch - Non-TTY execution
Binci now automatically detects whether or not it's running in a TTY, and launches docker with the appropriate interactive/TTY flags. This allows execution in environments where a TTY is not available, without resorting to screen or tmux hacks.
Patch - Binci Init
Fixes generated output from binci init command:
- before:
- - echo "before..."
- after:
- - echo "after..."
+ before: |
+ echo "before..."
+ after: |
+ echo "after..."