mirror of
https://gh.wpcy.net/https://github.com/discourse/discourse.git
synced 2026-05-03 11:47:35 +08:00
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. |
||
|---|---|---|
| .. | ||
| docker | ||
| annotaterb | ||
| bundle | ||
| dev | ||
| ember-cli | ||
| lint | ||
| notify_file_change | ||
| pitchfork | ||
| qunit | ||
| rails | ||
| rake | ||
| rspec | ||
| rubocop | ||
| system_rspec | ||
| turbo_rspec | ||
| unicorn | ||