From e3af02358287087fc8f89ba13765589e05d1c1a5 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 30 May 2026 11:45:45 +0000
Subject: [PATCH] Fix run.sh: always run pip install, not only on venv creation

Existing .venv without packages caused ModuleNotFoundError. pip install
is a no-op when everything is already up to date, so always running it
is safe and ensures deps are present.

https://claude.ai/code/session_01JuRTR5Xjx8emQsyerBgGU7
---
 run.sh | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/run.sh b/run.sh
index ee2a740..d61fb8b 100644
--- a/run.sh
+++ b/run.sh
@@ -1,5 +1,5 @@
 #!/bin/bash
-# Run ClubLedger – creates a virtualenv on first run, then starts the server.
+# Run ClubLedger – creates a virtualenv if needed, ensures deps are installed, starts the server.
 set -e
 
 VENV=".venv"
@@ -7,9 +7,8 @@ VENV=".venv"
 if [ ! -d "$VENV" ]; then
     echo "Creating virtual environment..."
     python3 -m venv "$VENV"
-    echo "Installing dependencies..."
-    "$VENV/bin/pip" install --quiet -r requirements.txt
-    echo "Done."
 fi
 
+"$VENV/bin/pip" install --quiet -r requirements.txt
+
 exec "$VENV/bin/python" main.py "$@"