zeppelin/docker/production/start-bot.sh

#!/bin/bash

# This wrapper script is used to run different things based on the DEBUG env variable
# Exec is used to forward signals: https://unix.stackexchange.com/a/196053

cd /zeppelin/backend
if [ "$DEBUG" == "true" ]; then
  echo "DEBUG MODE: Starting bot container without starting the bot"
  exec tail -f /dev/null
else
  echo "Starting bot"
  exec npm run start-bot-prod
fi
feat: more work on prod docker setup 2022-08-06 22:18:21 +03:00			`#!/bin/bash`

refactor: change how DEBUG behaves in prod The env var now only affects the bot container, not the API. This is because we don't currently need this extra debug information for the API. For the bot, with DEBUG set, the bot container will now start and do nothing. To start the bot in this container in debug mode, open a shell into the container and run the start-bot-prod-debug script manually. This change was made to allow more control over what profiling scripts and other things are run in the debug environment. 2023-06-26 19:35:19 +00:00			`# This wrapper script is used to run different things based on the DEBUG env variable`
			`# Exec is used to forward signals: https://unix.stackexchange.com/a/196053`
feat: more work on prod docker setup 2022-08-06 22:18:21 +03:00
			`cd /zeppelin/backend`
fix: clinic.js 0kb output files Something in our signal handlers/code that touched signal handlers conflicted with clinic.js's signal handler code. With this commit, we don't touch signal handlers at all if DEBUG mode is enabled. 2023-06-26 19:55:16 +00:00			`if [ "$DEBUG" == "true" ]; then`
refactor: change how DEBUG behaves in prod The env var now only affects the bot container, not the API. This is because we don't currently need this extra debug information for the API. For the bot, with DEBUG set, the bot container will now start and do nothing. To start the bot in this container in debug mode, open a shell into the container and run the start-bot-prod-debug script manually. This change was made to allow more control over what profiling scripts and other things are run in the debug environment. 2023-06-26 19:35:19 +00:00			`echo "DEBUG MODE: Starting bot container without starting the bot"`
			`exec tail -f /dev/null`
debug: add clinic.js for debugging 2023-04-04 20:44:13 +03:00			`else`
			`echo "Starting bot"`
			`exec npm run start-bot-prod`
			`fi`
No results found.