mini_portile | mini_portile and mini_portile2 - Simple autoconf builder | Runtime Evironment library

Try updating your Gemfile to use json@1.8.2 instead of 1.8.1 - according to this thread Ruby 2.2.x is incompatible with json 1.8.1.

1.8.2 should be functionally similar and not affect any of your other dependencies.

You can also run bundle update json to let bundler try to fix it for you - but that may put you at a much later version than 1.8.2, I'm not sure.

No harm in trying a couple things and reverting your changes.

Make process cannot find the mkdir command.

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

You have issues with libxml2

Make sure you have xcodebuild installed:

It seems like label(name, options.delete(:label)) is delegating with a nil arg. Your options in your haml is {:include_blank => true}. There is no label key in the hash. You should rather use options.fetch(:label, {}).

Change your methods to:

You need to upgrade your postgres_ext gem.

You currently have Arel 4.0.2 instead and PostgresExt 2.0.0 installed.

I see that PostgresExt 2.1.3 says “Fixes Arel 4.0.1 issues”. https://github.com/DavyJonesLocker/postgres_ext/blob/master/CHANGELOG.md#213

Your version of PostgresExt is incompatible with the version of Rails you have installed. I came to this epiphany because of the stacktrace you recently added.

Try running bundle update json to force update the json gem. If that doesn't work, you can run gem clean, delete your Gemfile.lock and run everything again.

Edit: It looks like your bundler version isn't compatible with your version of rails. You can try to downgrade bundler by running:

1. gem install bundler --version '1.14.6'
2. gem uninstall bundler --version '2.0.1'

Also, is this a new project? If so, you should consider using rails 5. Rails 3 is close to being three major versions behind with the release of rails 6 not too far away. It would help avoid a lot of these gem issues as well.

SQLite does not work with Heroku as its disk based and Heroku uses an ephemeral file system.

SQLite runs in memory, and backs up its data store in files on disk. While this strategy works well for development, Heroku’s Cedar stack has an ephemeral filesystem. You can write to it, and you can read from it, but the contents will be cleared periodically. If you were to use SQLite on Heroku, you would lose your entire database at least once every 24 hours.

Even if Heroku’s disks were persistent running SQLite would still not be a good fit. Since SQLite does not run as a service, each dyno would run a separate running copy. Each of these copies need their own disk backed store. This would mean that each dyno powering your app would have a different set of data since the disks are not synchronized.

-Heroku Devcenter: SQLite on Heroku

Heroku provides Postgres as the free default database for rails which is as close to a recommendation as you can get.

If you are deploying to Postgres you should also be developing/testing on Postgres.

Differences between backing services mean that tiny incompatibilities crop up, causing code that worked and passed tests in development or staging to fail in production. These types of errors create friction that disincentivizes continuous deployment. The cost of this friction and the subsequent dampening of continuous deployment is extremely high when considered in aggregate over the lifetime of an application.
- https://12factor.net/dev-prod-parity

If you really want to stick with SQLite you need to configure the adapters properly: