Our Masto instance is still getting "/usr/bin/env: ‘ruby2.3’: No such file or directory" when trying to-be-crontabbed commands from the production guide such as "RAILS_ENV=production bundle exec rake mastodon:media:clear" as the mastodon user.

Ruby 2.3.1 is installed and any other command seems to use it just fine.

Help!

@HedgeMage it's not a ruby issue it's an env issue. 'which ruby2.3' probably isn't going to get you anything.
@trelane It didn't, and I'm still fighting with it. I'd like to get this fixed so we don't get delivery delays on FHE from not having run related jobs. Any suggestions? Or ping me on IRC for faster comms?