autoprefixer-rails | Autoprefixer for Ruby and Ruby on Rails | Application Framework library

The issue was related to environment variables and not being able to find the correct path for the gems. I found a solution and updated the schedule.rb file.

Ok, found the problem. Turns out that I had copied the setting config.session_store :cache_store in development.rb from a different project I had been working on. However, this setting was added as part of the StimulusReflex setup for that other project.

From the StimulusReflex docs:

Cookie-based session storage is not currently supported by StimulusReflex.

Instead, we enable caching in the development environment so that we can assign our user session data to be managed by the cache store.

The default setting for this option is cookie_store. By changing it to :cache_store without specifying a cache repo, it implements ActionDispatch::Session::CacheStore and defaults to storing it in Rails.cache, which uses the :file_store option, which dumps it in tmp/cache.

However, further down in development.rb, there is some conditional logic that assigns config.cache_store to :null_store if there is no caching-dev.txt file. This implements ActiveSupport::Cache::NullStore, which is "a cache store implementation which doesn't actually store anything."

So because I had not enabled caching with rails dev:cache for this project, the session cache was getting toasted with every request.

LESSON LEARNED: Be very careful when copying config settings from an old project to a new one!

Most likely you have some strong constraints on some particular gems in your Gemfile that's it's blocking bundle from updating a dependency.

Currently Ruby 3.0 is not supported with Rails, as there will be next release for Rails. You can do following and it works by installing dev branch of ruby 3. I used ruby 3.1.0dev (2021-02-14T05:09:08Z master ff527e7e32) [x86_64-darwin19] Following commands are with RVM you can use same with other softwares I tried by installing

Thanks to jonrsharpe comment, I reoriented my searches and found this blog post on heroku engineering blog. Eventually, as stated by jonrsharpe:

The Nginx buildpack won't have Ruby in at all - you need to do any building in the Ruby buildpack context, so all the static buildpack needs to do is serve the results.

Therefore, to launch my middleman build command, I needed to hook somewhere in the ruby buildpack thing. And in the "jekyll on heroku" link, everything is explained: one should override the assets:precompile rake task.

1. Add gem "rake" to my Gemfile (and bundle, of course)
2. Create a Rakefile with the assets:precompile task :

Thanks to @Les Nightingill, I found the issue.

It was not directly linked to assets generation, but the probleme was indicated at the first error line in the logs :

Fixed by removing all config.assets.precompile calls in config files and using app/assets/config/manifest.js instead.

cf https://github.com/rails/sprockets/blob/8fc492abde6b20afbe6fa5d5aa7d1085aafd3527/UPGRADING.md#manifestjs

Okay, after days of trying everything I could think of I tried something I'd already tested but with the correct syntax this time, I guess, because it works now.

Here is what I needed to add to Capistrano's config file to ensure Yarn was available when deploying:

As far as I get you want to push feature branch onto Heroku. Builds works only with master branch, so you want to do smth like this:

git push heroku sqlite_to_pg:master

Feel free to review docs Deploying with Git