Battles are active right now so this cannot be deployed yet, but shou…

…ld put the nail in the deploy issue coffin. Work for #97

service/autoupdate.sh

@@ -2,20 +2,22 @@
 set -e
 
 ###################################
+# Auto updater script for simple projects
+#
 # Set as a BOT USER cron job, with the
 # correct path, and your bot will
 # auto update if there's a version
 # change (or any package change)
 #
 # I set mine for every 2 minutes with a daily log cleanup. Ex:
-# 
+#
 # */2 *  *   *   * /path/to/this/autoupdate.sh >> /var/log/botupdate.log 2>> /var/log/botupdate.log
 # 0 2 * * * rm /var/log/botupdate.log
-# 
+#
 # - jakethedev
 ###################################
 
 cd /opt/deploy/beatbattlebot
 cp package.json package.old
 git pull &> /dev/null
-diff -w package.old package.json || systemctl restart beatbattlebot
+diff -w package.old package.json || systemctl --user restart beatbattlebot.service

service/beatbattlebot.service

@@ -15,4 +15,4 @@ RestartSec=60s
 #StandardError=file:/var/log/bot.err
 
 [Install]
-WantedBy=multi-user.target
+WantedBy=default.target

service/install-beatbattlebot.sh

@@ -1,20 +1,25 @@
 #!/usr/bin/env bash
-# SYSTEMD SETUP
+#### SYSTEMD SETUP
+# NOTE If you have 236+, uncomment the StandardOutput/Error lines in the
+# service if you'd like to output logs and errors to custom locations. Else
+# it's journalctl for you
 
-echo "Copying service file to /etc/systemd/system..."
+# Installation of the unit file
+TARGETDIR="$HOME/.config/systemd/user/"
+echo "Copying service file to user unit directory..."
 systemd --version
-# If you have 236+, uncomment the StandardOutput/Error lines in the service if you'd like to output
-# logs and errors to custom locations. Else it's journalctl for you
-sudo cp beatbattlebot.service /etc/systemd/system/
+cp beatbattlebot.service $TARGETDIR
 
-echo "Reloading daemon, enabling and starting beatbattlebot service"
-sudo systemctl daemon-reload
-systemctl status beatbattlebot # It should say 'not loaded'
-sudo systemctl enable beatbattlebot
-sudo systemctl start beatbattlebot
+# Enabling, activating, and kickstarting the unit file
+systemctl --user daemon-reload
+echo "=== The following should say 'not loaded', otherwise, good luck ==="
+systemctl --user status beatbattlebot # It should say 'not loaded'
+systemctl --user enable beatbattlebot
+systemctl --user start beatbattlebot
+echo "Sleeping, then checking status"
 sleep 1
-sudo journalctl -f 
-# You should see healthy output and a logged-in message
+systemctl --user status beatbattlebot # It should say 'not loaded'
 
-echo "Setting up logrotate"
-sudo ln -s $(pwd)/logrotate.beatbattlebot /etc/logrotate.d/
+# Quick logging config
+# echo "Setting up logrotate"
+# sudo ln -s $(pwd)/logrotate.beatbattlebot /etc/logrotate.d/

service/logrotate.beatbattlebot

@@ -5,7 +5,7 @@
 	notifempty
 	compress
 	postrotate
-    systemctl restart beatbattlebot
+    systemctl --user restart beatbattlebot
 	endscript
 }