Cli: Easier Fedora/RedHat install

[mariusa]

Please provide a .rpm for Fedora/RedHat workstations

https://devcenter.heroku.com/articles/heroku-cli#download-and-install

Thanks

[gautamcgoel]

Yes, all us Fedora users have been left out in the cold... :(

[walidhalabi]

There's lots of rpm-based distros, including CentOS, RedHat, Fedora, and SUSE. Many are used as production systems and therefore there's lots of developers using Fedora and similar.

[jdxcode]

we plan to do this relatively soon, but until then please use the standalone install: https://devcenter.heroku.com/articles/heroku-cli#standalone-version

[Vitorspk]

Please can post here when the version is up.

[bernardoha]

En Fedora 26 pude usar cliente heroku, aquí los pasos:
https://bernad10.wordpress.com/2017/09/20/cliente-heroku-en-fedora-26-con-git-subir-un-proyecto-java-a-la-nube/

[cben]

npm install heroku-cli requires a newer NodeJS than Fedora 26 has.
Above blog shows how to install upstream NodeJS; if you prefer to use only fedora packages, it's possible to install node 8.6 from rawhide.

[ibarrajo]

@cben I recommend to use the node version manager instead, it's quite easy

https://github.com/tj/n

sudo npm install -g n
sudo n stable
sudo npm install -g heroku-cli

Works on RHEL 7.4

[jdxcode]

don't use the npm version, use the standalone CLI which includes node:

wget https://cli-assets.heroku.com/heroku-cli/channels/stable/heroku-cli-linux-x64 -O heroku.tar.gz
tar -xvzf heroku.tar.gz
mkdir -p /usr/local/lib /usr/local/bin
mv heroku-cli-v6* /usr/local/lib/heroku
ln -s /usr/local/lib/heroku/bin/heroku /usr/local/bin/heroku

[ibarrajo]

@jdxcode I saw the documentation and the reason for which not to use the npm version was unclear, I update my global packages constantly and the standalone version didn't seem to support self updates.

Am I mistaken or is there another reason all together for which to avoid using the npm version?

[jdxcode]

The main reason is because you can’t use an older version of node alongside the CLI in case you ever need to do that. It also won’t auto update and the standalone will.

[ppp0]

How 'bout
docker run --rm -it wingrunr21/alpine-heroku-cli

Needs docker, of course

[cben]

Does this container allow authenticating once and storing the auth for
later runs?
I.e. can you just alias heroku "docker run ..." ?

I think there are a few commands that want access to local filesystem (eg.
heroku git, heroku local) — is a container easy to use for these?

But all that dockerfile does is yarn global add heroku-cli
https://hub.docker.com/r/wingrunr21/alpine-heroku-cli/~/dockerfile/
which also works for me without docker
[EDIT: I'm on Fedora 27, have yarn 1.1.0 installed from npm, and I have succesfully installed heroku-cil via npm before anyway]

[ppp0]

Excellent tip, @cben

[heyakyra]

any progress on this?

[jdxcode]

while we'd like this, we're currently not planning on doing this any time soon frankly

[heyakyra]

oh...what happened to

we plan to do this relatively soon

?

[abhishekgupta5]

Anything on this ?

[jdxcode]

we did make the standalone install much easier recently:

curl https://cli-assets.heroku.com/install.sh | sh

[yzgyyang]

we did make the standalone install much easier recently

Worked on Fedora 28! Can we document supported os of this script, other than just "standalone install"?

[xmeng1]

I prefer to install by the tarball. just add the bin path to $PATH

~/.bash_profile

add one line

export PATH=$PATH:~/Applications/heroku/bin

apply it

source ~/.bash_profile

[PrateekArora03]

curl https://cli-assets.heroku.com/install.sh | sh

[fmorato]

To install under local user:

curl -L https://cli-assets.heroku.com/heroku-linux-x64.tar.gz | tee ~/heroku.tar.gz | tar xz -C ~/.local/share/
ln -s ~/.local/share/heroku/bin/heroku ~/.local/bin/
rm ~/heroku.tar.gz