Don't use foreman when running in SINGLE_DYNO mode

Author: Vidas P

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 
 ## [current]
+### Fixed
+- Don't use `foreman` to manage multiple processes when running with `SINGLE_DYNO=1`.
 
 
 ## [0.9.9.2] - 2020-09-09

Gemfile

@@ -71,13 +71,13 @@ gem 'jquery-datatables', '~> 1.10.19'
 gem 'grape', '~> 1.3.2'
 gem 'grape-entity', '~> 0.8.0'
 gem 'jwt', '~> 2.2.1'
-gem 'foreman', '~> 0.87.1'
 
 group :development do
   gem 'bullet', '~> 6.1.0'
   gem 'sqlite3', '~> 1.4.2'
   gem 'better_errors', '~> 2.7.0'
   gem 'binding_of_caller', '~> 0.8.0'
+  gem 'foreman', '~> 0.87.1'
   gem 'guard', '~> 2.16.2'
   gem 'guard-livereload', '~> 2.5.2'
   gem 'guard-rspec', '~> 4.7.3'

docker/scripts/init

@@ -40,9 +40,20 @@ if [ -z "${DO_NOT_SEED}" ]; then
 fi
 
 # Start ActiveWorkflow
+
+# When SINGLE_DYNO=1 run all the processes in the same container. This should
+# only be used for testing/demonstration purposes. SINGLE_DYNO mode was
+# added specifically to support running ActiveWorkflow on Heroku free plan.
+# Please use multiple container configuration in production.
+
 if [ -z "${SINGLE_DYNO}" ]; then
   # Web only
   exec bundle exec puma
 else
-  exec bundle exec foreman start
+  # Simple "homegrown" process management with somewhat graceful shutdown.
+  (until bundle exec puma; do sleep 1; done) &
+  web_id=$!
+  (until bundle exec rails runner bin/scheduler.rb; do sleep 1; done) &
+  (until bundle exec script/delayed_job -n 2 run; do sleep 1; done) &
+  wait $web_id
 fi