You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The SolidQueue background job does not reference the environment in RAILS_ENV #8
I’m reporting an issue with some behavior that seems off.
In the unit file you created, RAILS_ENV is set to Capistrano’s stage.
However, Capistrano’s stage does not necessarily correspond to the RAILS_ENV.
Thanks for the report, you're right: the stage name isn't necessarily the Rails environment.
#9, now merged into main, makes the systemd service use fetch(:rails_env, fetch(:stage)), the same rule as capistrano-rails and capistrano3-puma: RAILS_ENV falls back to the stage only when :rails_env isn't set. It will ship in the next release.
Activity
burisu commentedon Nov 9, 2026
Thanks for the report, you're right: the stage name isn't necessarily the Rails environment.
#9, now merged into main, makes the systemd service use
fetch(:rails_env, fetch(:stage)), the same rule ascapistrano-railsandcapistrano3-puma:RAILS_ENVfalls back to the stage only when:rails_envisn't set. It will ship in the next release.