guard-minitest | Guard : : Minitest automatically run your tests | Testing library

Based on the Gemfile (note correct spelling—not GemFile), it appears that the version of Puma is wrong. If you’re using a Gemfile.lock with a different version, that could account for the error. Also, your rails gem appears to be commented out, which is unlikely to be right.

One step you’re likely to need is this:

Ensure ‘mysql2’ is included in your gem file and run bundle install

The key part of the error message is:

From here: https://wikimatze.de/installing-postgresql-gem-under-ubuntu-and-mac/

Try the following:

1. Heroku runs bundle install when you push the code so you dont need to run this.

2. Did you run heroku run db:seed to actually seed your database?

3. If you did, you can run heroku run rails c, then u = User.all and manually check by looking at the output that the users have correctly been seeded.

4. (opinion) I would suggest using the "devise" gem for users/logins etc.. but feel free to use whatever you are more confortable with.

5. Please use the heroku logs to give us (and yourself) a better understanding of what is wrong by running heroku logs -n 200, 200 being the number of lines to display.

Have you run rails g foundation:install after upgrading foundation-rails to a new major version? I lost a lot of time on this same issue today until I realized that the new major version shifted the structure around. Running the installation command (and figuring out what conflicts it should override) fixed it for me.

I solved it. I just added the railties gem to the Gemfile, just below the rails gem, i.e.:

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:

As this lines says: Sprockets::FileNotFound: couldn't find file 'turbolinks' with type 'application/javascript'.

turbolinks gem is missing in your gemfile, maybe including it in your gemfile solves the issue.

The gem web-console is locking your update process, first change it to a more recent version like: