Starting to play with Katello 4.1 on a test server.
When I run foreman-rake console, I get a message about the foreman directory being non-writeable. Is this a concern, or is this expected behavior now with version 4.x?
[root@gray01 ~]# foreman-rake console
`/usr/share/foreman` is not writable.
Bundler will use `/tmp/bundler20210713-8221-bhu7yd8221' as your home directory temporarily.
Loading production environment (Rails 6.0.3.7)
irb(main):001:0>
When I exit, I get more fun:
rake aborted!
Errno::EACCES: Permission denied @ rb_sysopen - /usr/share/foreman/config/irbrc_history
/opt/theforeman/tfm/root/usr/share/gems/gems/railties-6.0.3.7/lib/rails/commands/console/console_command.rb:70:in `start'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties-6.0.3.7/lib/rails/commands/console/console_command.rb:19:in `start'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties-6.0.3.7/lib/rails/commands/console/console_command.rb:102:in `perform'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties-6.0.3.7/lib/rails/command/base.rb:69:in `perform'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties-6.0.3.7/lib/rails/command.rb:46:in `invoke'
/usr/share/foreman/lib/tasks/console.rake:5:in `block in <top (required)>'
/opt/rh/rh-ruby27/root/usr/share/gems/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => console
(See full trace by running task with --trace)