-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install foreman #246
Install foreman #246
Conversation
This only adds it for Debian because I don't have access to OS X right now and don't know how to install foreman on OS X. Commits welcome! |
The Foreman repo mentions http://assets.foreman.io/foreman/foreman.pkg . I don't know what to do with one of these but I hope someone knowledgable of OS X can point me in the right direction. |
I'm guessing we'd install it via homebrew. I'll take a look at this and add it to this PR when I've got time for laptop and an osx machine in front of me. update: Oops, I just read the comments and didn't look at the commits, sorry. I'll take a look anyway. |
@djcp please take a look anyway; anything to improve this, especially for OS X, would be super helpful. Should this be idempotent? In that case we should check for the existence of |
@mike-burns any reason why you'd install via a package manager? Looks like |
@seanpdoyle gem(1) is for installing libraries for use in the project you're working on (or, really, it's a low-level tool used by Bundler). It most certainly is not for installing executables, and the Rubygems team has maintained this stance. The biggest issues with installing an executable using gem(1) are that you don't get the manpages, and the executable is tied to the version of Ruby that gem(1) knows about. For a Ruby developer, this last one is a non-starter. Also, scroll up a little bit from the link you sent; it recommends installing it on OS X using the package manager. |
@mike-burns that's interesting. @croaky are there any debian / homebrew packages for |
Wait - foreman is installed as part of the heroku toolbelt on debian, and probably osx. You can confirm this by spinning up one of our vagrant boxes with laptop applied, and It's heroku's version, not debian's. I'm OK with that.
|
Well how about that:
I've updated the Debian part. Can someone confirm whether the Heroku Toolbelt as installed on OS X also installs foreman by default? |
I tried the command from this pull request to install foreman and can confirm that it worked. However, as discussed previously, the standalone Heroku toolbelt installer for OS X does NOT install foreman, so we do need the command from the current changeset. |
OK, so this PR is still needed to get foreman on OS X. Good to merge? |
It looks good to me. |
After asking for |
Opened #248 to resolve this. |
We use foreman on every project, so install it on every dev environment.