From 65fb4c9919ca73faaae244eb3694e91436e39312 Mon Sep 17 00:00:00 2001
From: FrozenFOXX <frozenfoxx@churchoffoxx.net>
Date: Thu, 31 May 2018 16:12:45 -0500
Subject: [PATCH] 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.
---
 scripts/vmpooler.service | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/vmpooler.service b/scripts/vmpooler.service
index e52643d41..de1281fee 100644
--- a/scripts/vmpooler.service
+++ b/scripts/vmpooler.service
@@ -6,7 +6,7 @@ After=basic.target network.target
 [Service]
 EnvironmentFile=-/etc/default/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
 KillMode=process