From c484cb9d4917229f5d19511be1056d00a13560e1 Mon Sep 17 00:00:00 2001
From: Timothy Kim <timothykim@fastmail.fm>
Date: Fri, 13 Mar 2026 12:23:20 -0400
Subject: [PATCH] fix git-crypt status check and remove pre-created docker
 network

git-crypt status outputs "    encrypted:" not "***ENCRYPTED***".
The shared docker network is created by nginx's compose file, so
pre-creating it caused a label mismatch that prevented containers
from starting.
---
 setup.sh | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/setup.sh b/setup.sh
index f1e021d..e535216 100644
--- a/setup.sh
+++ b/setup.sh
@@ -39,7 +39,7 @@ fi
 # --- Unlock git-crypt via Bitwarden ---
 
 cd "$REPO_DIR"
-if git-crypt status 2>/dev/null | grep -q '^\*\*\*ENCRYPTED\*\*\*'; then
+if git-crypt status 2>/dev/null | grep -q '    encrypted:'; then
     echo "==> Fetching git-crypt key from Bitwarden..."
     echo "    Log in to Bitwarden when prompted."
     if bw status 2>/dev/null | grep -q '"status":"unauthenticated"'; then
@@ -87,9 +87,6 @@ chown -R deploy:deploy /home/deploy/.ssh
 echo "==> Making scripts executable..."
 chmod +x "$REPO_DIR/scripts/"*.sh
 
-echo "==> Creating shared Docker network..."
-docker network create shared 2>/dev/null || true
-
 echo "==> Logging into Gitea registry..."
 echo "Run manually: docker login git.timothykim.net"