This PR fixes the problem that when a RAILS_MASTER_KEY is defined with the key for production in .env (which is the case when using Kamal for deployment), the script in bin/dev will start foreman which will then pick up the variables from .env leading to a ActiveSupport::MessageEncryptor::InvalidMessage error when running bin/dev
Kamal is added by default for new Rails apps >= v8 (see https://github.com/rails/rails/pull/51798). Although, it seems that is not fully initialized and the .env file generated by kamal init is removed when a new Rails app is generated.
--
There are several other problems with the .env approach of Kamal, so I'm not entirely sure if this PR is the "correct" fix, but is seems reasonable as bin/dev is only run locally to start bundling + rails.
TL;DR;
This PR fixes the problem that when a
RAILS_MASTER_KEYis defined with the key for production in.env(which is the case when using Kamal for deployment), the script inbin/devwill start foreman which will then pick up the variables from.envleading to aActiveSupport::MessageEncryptor::InvalidMessageerror when runningbin/devKamal is added by default for new Rails apps >= v8 (see https://github.com/rails/rails/pull/51798). Although, it seems that is not fully initialized and the
.envfile generated bykamal initis removed when a new Rails app is generated.--
There are several other problems with the
.envapproach of Kamal, so I'm not entirely sure if this PR is the "correct" fix, but is seems reasonable asbin/devis only run locally to start bundling + rails.See other:
--env /dev/nullsolution).envin Kamal is dangerous)