ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit` (ArgumentError)

[Yannick138]

2025-02-03 18:59:59 bin/rails aborted!
2025-02-03 18:59:59 ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit` (ArgumentError)
2025-02-03 18:59:59 
2025-02-03 18:59:59           raise ArgumentError, "Missing `secret_key_base` for '#{Rails.env}' environment, set this string with `bin/rails credentials:edit`"
2025-02-03 18:59:59                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-02-03 18:59:59 /rails/config/environment.rb:5:in `<main>'
2025-02-03 18:59:59 Tasks: TOP => db:prepare => db:load_config => environment
2025-02-03 18:59:59 (See full trace by running task with --trace)

When I do rake secret as suggested by the setup it says this:

rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
/usr/share/gems/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
yf@fedora:~$ 

[mrysav]

Hello!

Looks like I need to update the docs! How about running bin/rails secret from within the cloned repository? That should give you a new secret. You can set the SECRET_KEY_BASE environment variable to the random value that gives you.