rack-cors | Rack Middleware for handling Cross | Runtime Evironment library

First of all, the message about DidYouMean is a deprecation warning not an error, it doesn't break your app. It means that usage of DidYouMean::SPELL_CHECKERS is deprecated and will be removed in a future version of ruby. In this case in Ruby 3.3. You shouldn't worry about it until you use versions that are lower than 3.3. It's not your code that triggers the warning. It comes from a gem named Thor. The issue was solved in thor version 1.2.0. You can update the gem by calling bundle update thor.

The actual error comes from the bootsnap gem:

I finally got to the bottom of this.

Chrome will still use the cached header even if the origins differ and the Vary header is present and set to 'Origin' if the ETags still match.

To get past this either unset the ETag header or vary it based on request origin.

Use gemsets to avoid accidentally changing ruby versions, but for now use the command:

As you can see what they use in the linked rack-cors issue is of a Regexp class, and not a String as in your case.

I suggest concatenating 2 environment variables:

• STRING_DOMAIN_CORS="https://example1.com, https://example2.com"
• REGEXP_DOMAIN_CORS="(.*?).example.com"

and map them accordingly:

I'm assuming you've downloaded and installed PostgreSQL on your system. Use the following to point the gem to where postgres is installed. This is an example of what it'd look like on my system.

It complains that Access-Control-Allow-Origin header value is too broad: it's set to the wildcard * which means that everyone can make a request to your server. There are two ways of solving this problem

• Either set Access-Control-Allow-Origin to something like [localhost:3000] instead of the wildcard, so you client (running on localhost:3000) could request the server.

• Or set withCredentials=false mode on your client side. I usually use axios and and do something like this

Your error is in the last line;

/var/www/swan/code/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require': cannot load such file -- listen (LoadError)

bundle install --deployment --without development test command install only production and general gems. Does not install the development or test gems. Rails read environment variables RAILS_ENV for the setting environment. RAILS_ENV variable if not set rails default accept development. And bundler try to load all gems + development group gems. But bundle install --deployment --without development test command only install production and general gems. So listen gem is not installed because listen gem in development group. RAILS_ENV=production bin/rails c command not throw error because not try to load development gems.

You have spring in your gemfile, usually hanging consoles and servers are related to that. The webrick gem was removed from the standard library in Ruby 3, so that's why it needs to be included in your Gemfile.

Re-add webrick to your Gemfile, do a bundle install, and then stop the background spring server with bin/spring stop. Then re-run the server.

Your best bet on solving issues with spring would be to head over and read about the gem on the GitHub project page, or opening a new question here on SO.

In your project directory, try installing rails gem install rails -v 4.1.6 and removing the version from the failing gems like (liquid_markdown, gon, etc..) then try running bundle update then bundle clean --force

I think this might be an issue because all the version of these gems are locked inside your Gemfile