We have three main ways of running rake commands in 1.2:
bundle exec rakeon source or Debian installs
scl enable ruby193 'rake ..'or
ruby193-rakeon EL6 or SCL installs
rakeon Fedora installs
Personally I've found it hard to write docs for these as every time a rake command is mentioned, I have to explain which variant to use on which OS. If we didn't, people would copy and paste and it wouldn't work.
Solution: add a foreman-rake command, much like ruby193-rake, but that runs the correct thing. We can change what command it runs via the packaging in exactly the same way as foreman.spec modifies dbmigrate today.
fixes #2684 - add foreman-rake script to /usr/sbin
#1 Updated by Dominic Cleal almost 10 years ago
Other nice enhancements would be:
- cd ~foreman first
- sudo or su to foreman, to prevent tmp/ permission problems and postgresql ident auth
- default to RAILS_ENV=production
#2 Updated by Dominic Cleal over 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Dominic Cleal
- Target version set to 1.3.0
#3 Updated by Dominic Cleal over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 86df2a8aa1664bb4320abcb461dff00569e43c16.
refs #2684 - add foreman-rake script to /usr/sbin