How to Push a Custom Gem to Heroku Master

Unable to push a custom gem to heroku master

When Heroku "reads" /home/nci/Zacchi/kuizu/gemz (or any other local reference) it doesn't know where to go. You need to publish your gem and remove the local reference from your Gemfile.

Timeout on Heroku push with a custom/private gem

So the problem ended up being that the version of git Heroku uses doesn't support using tokens yet! Once I included a username/password in my Gemfile (not happy about that but I have set up a special collaborator account so the security risk is narrowed somewhat...) it worked perfectly!

A special thanks to this question that I found that helped me out :)

How to get working a local gem on heroku?

I finally got it working.

My solution was use :git instead of :path

gem 'gem_name', '= 0.x.x', git: 'git://........../gem_name.git'

Installing a gem bundle in a python app on Heroku

Try explicitly selecting the python buildpack by using heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-python.git

It will still perform the detection process but I think (?) it will run the buildpack you've explicitly selected before or instead of attempting any others, and since you still have a python application installed, it should work.

Note that after you do the config:add you need to rebuild your slug on Heroku, which currently can ONLY be done by pushing an actual code change via git. You can make an empty git commit if you don't have any real changes to push, using git commit --allow-empty -m "Empty commit"

You can also create a new project using the --buildpack command line option.

Heroku push issue

Uglifier::Error: Unexpected token name «scoreName», expected punc «,».
To use ES6 syntax, harmony mode must be enabled with
Uglifier.new(:harmony => true)

You just need to change

config.assets.js_compressor = :uglifier

to

config.assets.js_compressor = Uglifier.new(harmony: true)

in production.rb (or the appropriate Heroku environment like staging.rb where the error is being thrown in the build pipeline)

Source

Heroku: push rejected - failed to install gems via bundler

I always just comment out the SQLite3 gem and it works well for me, so when I push to heroku my gemfile looks like this:

# Development Database
#gem 'sqlite3'
# Production Database
gem 'pg'

EDIT:

The above solution works, and is easy if you don't want to update your gems for whatever reason. The better long term solution to this problem is to do the following:

group :development, :test do
  gem 'sqlite3'
end
group :production do
  gem 'pg'
end

then delete your gemfile.lock file.
You'll need to generate a new gemfile.lock file that reflects your changes. In the terminal run:

bundle update

Finally, update your repository and push to heroku by doing the following in the terminal:

git add .
git commit -m "commit message"
git push heroku 

Git Push Heroku Master error in rubyonrails

First of all, I think Postgres is the issue here. I believe Heroku and Rails builtin PG causes some issue. Try editing your gem page like this:

group :development, :test do
     gem 'sqlite3'
end

group :production do
     gem 'pg'
     gem 'rails_12factor'
end

Then, do "bundle install".

If this doesn't work try doing "bundle install --without production"

Hope this helps.

Problem pushing a master to heroku

You're going off on the wrong path - Heroku doesn't run Sqlite, it runs PostgreSQL. When you deploy your app it creates a new database.yml file for you. So you shouldn't specify Sqlite in your gemfile - you should only specify it for your development environment.

Something like this:

group :production, :staging do
  gem "pg"
end

group :development, :test do
  gem "sqlite3-ruby", :require => "sqlite3"
end

If you want to read more about Heroku database stuff, go here.
I asked a similar question (and got my answer) here.

---

Related Topics