You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a bug yesterday, around all bin/sail calls to docker-compose, not using custom docker-compose files (i.e: docker-compose -f )
I looked at the 1.x branch source and you've fixed that, I think? export SAIL_FILES=${SAIL_FILES:-""}
These are DOCKER_COMPOSE_FILES really, rather than a new concept which is a SAIL_FILE which could be something different?
I was trying to explain to my team, today, that a SAIL_FILE is actually a DOCKER_COMPOSE_FILE, and I'm wondering if I'm correct, or I've overlooked some "sail magic" and it's not actually a docker-compose file, but something new?
Just looking for validation here, on naming
The text was updated successfully, but these errors were encountered:
Description:
I had a bug yesterday, around all
bin/sail
calls to docker-compose, not using custom docker-compose files (i.e: docker-compose -f )I looked at the 1.x branch source and you've fixed that, I think?
export SAIL_FILES=${SAIL_FILES:-""}
These are DOCKER_COMPOSE_FILES really, rather than a new concept which is a
SAIL_FILE
which could be something different?I was trying to explain to my team, today, that a SAIL_FILE is actually a DOCKER_COMPOSE_FILE, and I'm wondering if I'm correct, or I've overlooked some "sail magic" and it's not actually a docker-compose file, but something new?
Just looking for validation here, on naming
The text was updated successfully, but these errors were encountered: