mirror of
https://github.com/puppetlabs/vmpooler.git
synced 2026-01-26 10:08:40 -05:00
65fb4c9919
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.
14 lines
307 B
Desktop File
14 lines
307 B
Desktop File
[Unit]
|
|
Description=VmPooler
|
|
Wants=basic.target
|
|
After=basic.target network.target
|
|
|
|
[Service]
|
|
EnvironmentFile=-/etc/default/vmpooler
|
|
WorkingDirectory=/opt/vmpooler
|
|
ExecStart=/opt/vmpooler/vmpooler -s Puma -E production
|
|
ExecReload=/bin/kill -HUP $MAINPID
|
|
KillMode=process
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|