Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jkeam/fdda2557ee2a28881f5a33356391f42c to your computer and use it in GitHub Desktop.
Save jkeam/fdda2557ee2a28881f5a33356391f42c to your computer and use it in GitHub Desktop.
Installing a Gem on Heroku from a Private GitHub Repo

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.

  1. Generate an OAuth token from GitHub

  • You only need to check the repo scope when configuring the token permissions
  1. Update Gemfile to use your private repository

gem 'my_private_repo', git: 'https://github.com/username/my_private_repo.git'
  1. Configure bundler with your OAuth token

bundle config github.com <your_github_oauth_token>

Now bundle and if everything works locally you are ready to deploy to Heroku!

  1. Finally add BUNDLE_GITHUB__COM to your Heroku environment

$ heroku config:add BUNDLE_GITHUB__COM=<your_github_oauth_token>

You now have a private gem installed on Heroku!

Optional - configure bundler to use your local repo in development

bundle config has another option to work against your local git repository without updating your Gemfile The catch is that you need to specify the git branch when configuring the gem

gem 'my_private_repo', git: 'https://github.com/username/my_private_repo.git', branch: 'master'

Then run bundle config local.ecto </path/to/your/local/repo>

More information here - see the section "Local git repositories" at the end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment