make debugging optional with the puma image

Developers who need debugging should pass RUBY_DEBUG_OPEN or
RUBY_DEBUG_START at docker compose up time to enable the debugger.
Having it on by default caused some common developer operations
to have issues.

Change-Id: Ic7990f7276b714472a14ebb7cbc4900f09333407
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/340643
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Build-Review: James Butters <jbutters@instructure.com>
Product-Review: Keith Garner <kgarner@instructure.com>
Reviewed-by: Mysti Lilla <mysti@instructure.com>
QA-Review: Mysti Lilla <mysti@instructure.com>
This commit is contained in:
Keith T. Garner 2024-02-15 18:23:16 -06:00 committed by Keith Garner
parent 52e5546128
commit a92c06bd0b
1 changed files with 7 additions and 1 deletions

View File

@ -1,12 +1,18 @@
# to use this add docker-compose/puma.override.yml to your COMPOSE_FILE var in .env and rebuilid your web container
# When you use this container you can pass RUBY_DEBUG_OPEN=true or RUBY_DEBUG_START=true to a run of the container like:
# docker compose run -e RUBY_DEBUG_OPEN=true -P --rm web
#
# Altenatively you can uncomment the environment variable below, but that can cause issues if you run commands that kick
# off multiprocessing
version: '2.3'
services:
web:
build:
dockerfile: Dockerfile.puma
environment:
RUBY_DEBUG_OPEN: true
# RUBY_DEBUG_OPEN: true
RUBY_DEBUG_PORT: 12345
RUBY_DEBUG_HOST: 0.0.0.0
VIRTUAL_PORT: 80