procfile causes failure on Rails 8.0 about rails HOT 8 CLOSED

@dhh could this be the env.erb file being loaded by foreman and using an non-existent RAILS_MASTER_KEY?

@rubys can you see if by deleting that file before starting the server it works?

from rails.

@dhh I think the .env file picked up both by default by kamal and foreman might be a big source of confusion and bugs, vide basecamp/kamal#233 and basecamp/kamal#420

Can we maybe differentiate somehow those 2 env files so they do not interfere with each other?

from rails.

Neither deleting .env.erb or config/master.key solves this problem. I also wasn't seeing this problem on --main on Friday.

from rails.

Looks like the .env.erb gets rendered to .env, after removing that file foreman works again for me

from rails.

Confirming that the following fixes the problem for me:

erb .env.erb > .env

from rails.

Yeah, it seems kamal init is being called before we create the .env.erb template. So the .env has dummy values. But even if I swap the order of those calls, it seems kamal init is not template aware.

from rails.

Ah yeah, will add a call to evaluate .env.erb on first run. Then it'll yank the key from master.key into .env.

from rails.

I stumbled over the same problem when having credentials per environment. Forman always picked up the master key from .env (needed for kamal deployment) although running locally in development environment and config/credentials/development.key was present. I just forced foreman to not load any env file by adding --env /dev/null to the foreman command in bin/dev like this:

exec foreman start -f Procfile.dev --env /dev/null "$@"

This approach is mentioned here ddollar/foreman#702

from rails.