mroderick / codebar-planner

95%

master: 95%

LAST BUILD ON BRANCH remove-puma-cluster-mode-config

branch: remove-puma-cluster-mode-config

CHANGE BRANCH

x

Reset

Sync Branches

• remove-puma-cluster-mode-config
• add-docs
• add-editor-config
• add-scout-apm
• add-sitemap-generator
• attempt-to-fix-issue-template
• bundle-ignore-junk
• fix/event-description-xss-vulnerability
• freeze-postgres-version
• imagemagick-check
• improve-intro-text
• improve-language
• improve-repository-configs
• increase-delayed-job-max-runtime
• issue-2367-workshop-feedback
• link-to-chapters-from-pills
• lock-gem-platforms
• make-event-rendering-faster
• optimise-images
• policy-tests
• remove-2024-impact-report-banner
• remove-bootsnap
• remove-go-squared
• remove-google-analytics
• remove-meta-partial
• remove-skylight
• remove-twitter
• remove-unused-i18n-features
• remove-unused-new-relic
• speedup-ci-tests
• stop-pinning-image-processing
• update-year-for-impact-report
• upgrade-ruby
• use-playwright
• use-rails-7-1-defaults

Build # 21563977310

Build Type

push

github

Committed by mroderick

Commit Message

Remove unused Puma cluster mode configuration

This removes the preload_app! directive and on_worker_boot block from
config/puma.rb. These cluster-mode features are not used since the
application runs in single-process mode (no workers configured).

VERIFICATION THAT CLUSTER MODE IS NOT USED:

1. No 'workers' setting in config/puma.rb - cluster mode requires
   explicitly setting 'workers N' where N > 0. Without this, Puma
   runs in single-process mode by default.

2. No WEB_CONCURRENCY environment variable - searched entire codebase,
   no references found. This is Heroku's standard variable for
   controlling worker count.

3. Procfile uses standard single-process command:
   'bundle exec puma -C config/puma.rb' with no worker-related flags.

4. No environment-specific Puma configs - only config/puma.rb exists,
   no production/staging overrides.

5. Environment configs (development/production/test.rb) have no Puma
   worker configuration.

6. The Puma 7.2.0 warning itself confirms the on_worker_boot block
   "will not execute in the current Puma configuration."

IMPACT:

- No behavior change - this code was never executing
- Removes warning introduced in Puma 7.x about unused callbacks
- Prepares for Puma 8.0 where on_worker_boot will be removed entirely
- If cluster mode is needed in future, these are standard patterns
  that can be easily restored

Related to https://github.com/codebar/planner/pull/2447

Run Details

3242 of 3406 relevant lines covered (95.18%)

81.62 hits per line