Add sidekiq_service_unit_env_vars option to pass Environment variable…

[Paprikas]

…s to systemd config file.

I'm using RBENV. And this guy requires some variables to run.

Usage example:

SSHKit.config.command_map[:bundler] = "#{fetch(:rbenv_path)}/bin/rbenv exec bundler"
set :sidekiq_service_unit_env_vars, [
  "RBENV_VERSION=#{fetch(:rbenv_ruby)}",
  "RBENV_ROOT=#{fetch(:rbenv_path)}"
]

Now after bundle exec cap production sidekiq:install proper config will be generated.

  ExecStart=/usr/local/rbenv/bin/rbenv exec bundler exec sidekiq -e production....
  Environment=RBENV_VERSION=2.7.1
  Environment=RBENV_ROOT=/usr/local/rbenv

[mrudult]

We need this PR too!

In our case, Sidekiq v6 didn't start as it required HOME environment variable to be set to the deploying user's home directory.

So we had to manually add that to the systemd unit file:

Environment="HOME=/home/deploy"