bug: fix from renaming teams

Author: lukepolo

hasura/triggers/match_lineups.sql

@@ -0,0 +1,20 @@
+CREATE OR REPLACE FUNCTION public.tbu_match_lineups()
+RETURNS trigger
+LANGUAGE plpgsql
+AS $$
+DECLARE
+    _match_status text;
+BEGIN
+    IF NEW.team_name != OLD.team_name  THEN
+        select status from matches where lineup_1_id = NEW.id or lineup_2_id = NEW.id into _match_status;
+        IF _match_status NOT IN ('PickingPlayers', 'Scheduled', 'WaitingForCheckIn', 'Veto', 'WaitingForServer') THEN
+            RAISE EXCEPTION 'Cannot change the name of a lineup when the match is Live or Finished' USING ERRCODE = '22000';
+        END IF;
+    END IF;
+
+    RETURN NEW;
+END;
+$$;
+
+DROP TRIGGER IF EXISTS tbu_match_lineups ON public.match_lineups;
+CREATE TRIGGER tbu_match_lineups BEFORE INSERT OR UPDATE ON public.match_lineups FOR EACH ROW EXECUTE FUNCTION public.tbu_match_lineups();

src/configs/s3.ts

@@ -7,7 +7,7 @@ export default (): {
     key: process.env.S3_ACCESS_KEY,
     secret: process.env.S3_SECRET,
     bucket: process.env.S3_BUCKET,
-    db_backup_bucket: process.env.S3_DB_BACKUP_BUCKET,
+    db_backup_bucket: process.env.S3_DB_BACKUP_BUCKET || "5stack-db-backups",
     endpoint: process.env.S3_ENDPOINT || process.env.DEMOS_DOMAIN,
     useSSL: process.env.S3_USE_SSL === "false" ? false : true,
     port: process.env.S3_PORT || "443",