To verify your CLI installation, use the heroku -version command: $ heroku -version This method can cause issues if the CLI’s dependencies become incompatible in minor or patch releases. If you use any of the other installation methods, it includes the proper version of Node.js and doesn’t conflict with any other version on your system.Īlso, this method doesn’t use the yarn lockfile for dependencies like the others do, even if you install with yarn. Heroku uses current releases of Node.js and doesn’t support older versions. It also requires you to use your system’s version of Node.js, which can be older than the version Heroku develops the CLI against. This installation method doesn’t autoupdate. It’s strongly recommended to use one of the other installation methods if possible. This method is also useful if you want fine-grained control over CLI updates such as in a tested script. You must have node and npm installed already. ARM and BSD must use this installation method. Use this manual install method in environments where autoupdating isn’t ideal, or where Heroku doesn’t offer a prebuilt Node.js binary. The CLI is built with Node.js and installable via npm. Install the community-maintained heroku-cli 7.60.1-1: $ yay -S heroku-cli Use the standalone installation for an autoupdating version of the CLI. Install with Ubuntu / Debian apt-get $ curl | sh xz is much smaller but gz is more compatible. These tarballs are available in gz or xz compression. You can also download one of the following tarballs and extract it yourself. The script requires sudo and isn’t Windows compatible. To set up the CLI in /usr/local/lib/heroku and /usr/local/bin/heroku, run the following script. It contains its own node.js binary and autoupdates. The standalone install is a simple tarball with a binary. Download the appropriate installer for your Windows installation:ģ2-bit installer Standalone Installation with a Tarball
0 kommentar(er)
