Project

General

Profile

Actions

Feature #2684

closed

foreman-rake command

Added by Dominic Cleal over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Packaging
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We have three main ways of running rake commands in 1.2:

  • bundle exec rake on source or Debian installs
  • scl enable ruby193 'rake ..' or ruby193-rake on EL6 or SCL installs
  • rake on 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.

Actions #1

Updated by Dominic Cleal over 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
Actions #2

Updated by Dominic Cleal over 10 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Dominic Cleal
  • Target version set to 1.3.0
Actions #3

Updated by Dominic Cleal over 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF