Update to generic launcher

I realized the launcher itself handles looking up the Ruby interpreter with /usr/bin/env ruby. Manually specifying an interpreter is going to try to circumvent that and isn't nearly as portable as an example service. By moving this sample script back to the generic launcher directly a user can choose to handle how /usr/bin/env looks up Ruby, whether it's with a jruby installation, rbenv, or however the user wishes.
This commit is contained in:
FrozenFOXX 2018-05-31 16:12:45 -05:00 committed by mattkirby
parent 9b8b35395d
commit 65fb4c9919

View file

@ -6,7 +6,7 @@ After=basic.target network.target
[Service] [Service]
EnvironmentFile=-/etc/default/vmpooler EnvironmentFile=-/etc/default/vmpooler
WorkingDirectory=/opt/vmpooler WorkingDirectory=/opt/vmpooler
ExecStart=/opt/jruby/bin/jruby /opt/vmpooler/vmpooler -s Puma -E production ExecStart=/opt/vmpooler/vmpooler -s Puma -E production
ExecReload=/bin/kill -HUP $MAINPID ExecReload=/bin/kill -HUP $MAINPID
KillMode=process KillMode=process