docker-container-entry.sh

#!/bin/bash
# https://stackoverflow.com/questions/35022428/rails-server-is-still-running-in-a-new-opened-docker-container#35023225

set -e

## For thin dev server:
if [ -f tmp/pids/server.pid ]; then
  rm tmp/pids/server.pid
fi

# built_lock_file="/tmp/generated/yarn.lock"
# current_lock_file="yarn.lock"

# # Restore dirs/files that get removed when mounting volume because the local dev machine
# # doesn't have them.
# # See https://nickjanetakis.com/blog/dealing-with-lock-files-when-using-ruby-node-and-elixir-with-docker
# function cp_node_modules() {
#   echo "Restoring node modules (might take a while) ..."
#   cp -p "${built_lock_file}" .
#   # TODO: Consider using rsync to speed things up
#   rm -rf node_modules
#   cp -Rp /tmp/generated/node_modules .
# }

if [ "$1" != "bash" ]; then
  # Restore dirs/files that get removed when mounting volume if the host machine doesn't have them.
  # See https://nickjanetakis.com/blog/dealing-with-lock-files-when-using-ruby-node-and-elixir-with-docker
  echo "Restoring auto-generated files ..."
  cp -p /tmp/generated/Gemfile.lock .
  cp -p /tmp/generated/yarn.lock .

  # Not needed as long as it is blacklisted in `docker-compose-dev.yml`
  #rsync -ar /tmp/generated/node_modules/ node_modules/

  # if [ -f 'yarn.lock' ]; then
  #   if ! diff "${built_lock_file}" "${current_lock_file}" > /dev/null; then
  #     cp_node_modules
  #   fi
  # else
  #   cp_node_modules
  # fi
fi

exec bundle exec "$@"