Due to issues getting eye to work on the new machine, we tried moving from eye to systemd.
To make things easier, we also moved from unicorn to puma because there is better documentation around how to configure puma through systemd through capistrano.
This didn't work, because systemd doesn't have the necessary granularity of management to be able to cycle sidekiq and puma when they grow too memory-large...and thus we would encounter stability issues.
This also moved from eye-patch to eye because I was trying to troubleshoot issues with eye, and the indirection was causing problems.
Instead, we moved back to eye/unicorn, and fixed the issues which were originally preventing us from deploying to the new machines:
SSHKit::Backend::Netssh.config.pty = true in deploy.rb in order to prevent a hang during eye load config
A bug in wicked_pdf, which prevented it from calling wkhtmltopdf -V successfully (see initializer/wicked_pdf.rb).
Due to issues getting
eyeto work on the new machine, we tried moving fromeyetosystemd. To make things easier, we also moved fromunicorntopumabecause there is better documentation around how to configure puma through systemd through capistrano.This didn't work, because systemd doesn't have the necessary granularity of management to be able to cycle sidekiq and puma when they grow too memory-large...and thus we would encounter stability issues.
This also moved from
eye-patchtoeyebecause I was trying to troubleshoot issues witheye, and the indirection was causing problems.Instead, we moved back to eye/unicorn, and fixed the issues which were originally preventing us from deploying to the new machines:
SSHKit::Backend::Netssh.config.pty = trueindeploy.rbin order to prevent a hang duringeye load configwkhtmltopdf -Vsuccessfully (see initializer/wicked_pdf.rb).