pvbackup: Fix REMOTE_X checks

Author: kallisti5

containers/tools/pvbackup/Makefile

@@ -2,3 +2,5 @@ VERSION = $(shell cat VERSION | grep -Ev "^#" | tail -1)-development
 REGISTRY = ghcr.io/haiku
 default:
 	podman build --no-cache --tag ${REGISTRY}/pvbackup:${VERSION} .
+push:
+	podman push ${REGISTRY}/pvbackup:${VERSION}

containers/tools/pvbackup/README.md

@@ -20,4 +20,5 @@ I'm a simple container to backup/restore encrypted persistant volume data to an
 #### Optional
 
 * REMOTE_NAME - name of remote specified in configuration file (defaults to "backup")
-* REMOTE_MAX_AGE - maximum backup age in bucket. ex: 30d,1y,etc
+* REMOTE_MAX_AGE - maximum backup age in bucket. example: 30d,1y,etc
+

containers/tools/pvbackup/VERSION

@@ -1,2 +1,2 @@
 # ONLY UPDATE ONCE READY TO BUILD NEW RELEASE
-3.0.1
+3.0.2

containers/tools/pvbackup/pvsync.sh

@@ -33,12 +33,12 @@ if [ ! -f $RCLONE_CONFIG_PATH ]; then
 	exit 1
 fi
 
-if [ ! -z "$REMOTE_PREFIX" ] ;then
+if [ -z "$REMOTE_PREFIX" ] ;then
 	echo "REMOTE_PREFIX is not defined!  This is the bucket name for s3 or other prefix path"
 	exit 1
 fi
 
-if [ ! -z "$REMOTE_NAME" ] ;then
+if [ -z "$REMOTE_NAME" ] ;then
 	echo "REMOTE_NAME is not defined. Defaulting to 'backup' (make sure this matches config file)"
 	REMOTE_NAME="backup"
 fi