The current Beanstalk solution stack for Ruby + Puma uses the configuration file at /opt/elasticbeanstalk/support/conf/pumaconf.rb
and ignores the config/puma.rb
inside the Rails application directory.
I could override the file above with a custom one via .ebextensions
but am hesitant because I'd like to avoid breakage in case the path to the PID or - more importantly - unix socket files changes in upcoming solution stack versions.
What is the best practice for customizing the Puma configuration on Beanstalk?