Skip to content
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

Merged
merged 0 commits into from
Jul 10, 2014
Merged

Install foreman #246

merged 0 commits into from
Jul 10, 2014

Conversation

mike-burns
Copy link
Contributor

We use foreman on every project, so install it on every dev environment.

@mike-burns
Copy link
Contributor Author

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!

@mike-burns
Copy link
Contributor Author

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.

@djcp
Copy link
Contributor

djcp commented Jul 8, 2014

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.

@mike-burns
Copy link
Contributor Author

@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 foreman before installing it.

@seanpdoyle
Copy link
Contributor

@mike-burns any reason why you'd install via a package manager? Looks like gem install is the preferred (and cross-platform) approach. https://github.com/ddollar/foreman#installation

@mike-burns
Copy link
Contributor Author

@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.

@seanpdoyle
Copy link
Contributor

@mike-burns that's interesting.

@croaky are there any debian / homebrew packages for suspenders or parity?

@djcp
Copy link
Contributor

djcp commented Jul 10, 2014

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 which foreman says it's in /usr/bin/

It's heroku's version, not debian's. I'm OK with that.

mkdir foreman-test
cd foreman-test
vagrant init thoughtbot/ubuntu-14-04-server-with-laptop
vagrant up
vagrant ssh
> which foreman

@mike-burns
Copy link
Contributor Author

Well how about that:

~% dpkg-query -s heroku-toolbelt
Package: heroku-toolbelt
Status: install ok installed
Priority: standard
Section: main
Maintainer: Heroku
Architecture: all
Version: 3.5.0
Depends: git-core, foreman, heroku (= 3.5.0)
Description: A metapackage for working with the Heroku platform.

I've updated the Debian part. Can someone confirm whether the Heroku Toolbelt as installed on OS X also installs foreman by default?

@jferris
Copy link
Contributor

jferris commented Jul 10, 2014

foreman is installed as part of the heroku toolbelt on debian, and probably osx.

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.

@mike-burns
Copy link
Contributor Author

OK, so this PR is still needed to get foreman on OS X. Good to merge?

@jferris
Copy link
Contributor

jferris commented Jul 10, 2014

It looks good to me.

@mike-burns mike-burns merged commit ffde1b2 into master Jul 10, 2014
@mike-burns mike-burns deleted the foreman-via-package-manager branch July 10, 2014 14:32
@seanpdoyle
Copy link
Contributor

$ cd laptop
$ bash mac
Changing your shell to zsh ...
Changing shell for seanpdoyle.
Password for seanpdoyle:
# ...
Installing foreman ...
installer: Must be run as root to install this package.
failed

After asking for sudo, installing foreman still failed

@mike-burns
Copy link
Contributor Author

Opened #248 to resolve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants