discourse/bin
Alan Guo Xiang Tan 63023145c2
DEV: Check RUN_PITCHFORK for explicit "1" value (#37264)
What is the problem?

We have a need to disable pitchfork via the `RUN_PITCHFORK` env.
However, `RUN_PITCHFORK` is checked for existence/non-emptiness in both
`bin/rails` and `config/unicorn_launcher`. This means setting
`RUN_PITCHFORK=0` enables pitchfork, which is counterintuitive.

What is the solution?

Change the checks to explicitly test for the value `"1"`. Now only
`RUN_PITCHFORK=1` enables pitchfork, while `0` or unset uses unicorn.
2026-01-23 09:30:28 +08:00
..
docker DEV: Add Pitchfork alongside Unicorn (#35370) 2025-10-24 11:08:23 +02:00
annotaterb DEV: fix linter and linting config (#36815) 2025-12-22 07:23:19 +11:00
bundle DEV: fix linter and linting config (#36815) 2025-12-22 07:23:19 +11:00
dev DEV: Add basic bin/dev script for launching in development (#23254) 2023-08-25 12:07:16 +08:00
ember-cli DEV: fix linter and linting config (#36815) 2025-12-22 07:23:19 +11:00
lint FIX: Add syntax_tree to lints and fix-all lefthook hooks (#37258) 2026-01-22 11:14:42 +08:00
notify_file_change FIX: notify_file_change was outputting a command to vim 2020-12-10 10:03:57 -05:00
pitchfork DEV: Add Pitchfork alongside Unicorn (#35370) 2025-10-24 11:08:23 +02:00
qunit DEV: Correct bin/qunit random seed handling (#37087) 2026-01-13 19:37:28 +00:00
rails DEV: Check RUN_PITCHFORK for explicit "1" value (#37264) 2026-01-23 09:30:28 +08:00
rake DEV: fix linter and linting config (#36815) 2025-12-22 07:23:19 +11:00
rspec DEV: Add client settled checks for system tests (#35230) 2025-10-10 11:03:18 +08:00
rubocop DEV: fix linter and linting config (#36815) 2025-12-22 07:23:19 +11:00
system_rspec DEV: Minimal first pass of rails system test setup (#16311) 2022-09-28 11:48:16 +10:00
turbo_rspec DEV: Enforce deprecation-free tests for preinstalled plugins/themes (#36445) 2025-12-16 17:48:29 -03:00
unicorn DEV: Extract unicorn server PID when ArgumentError raised (#36649) 2025-12-15 09:56:04 +10:00