runs reliably whether Vercel starts inside /site or at the repo root:

installCommand
 – If requirements.txt is in the current directory, install normally.
 – Otherwise it jumps up one level (the real project root) and installs from there.
buildCommand
 – Same logic for build.sh: run in place if it’s there, or cd .. and run.

Author: nembal

vercel.json

@@ -1,5 +1,5 @@
 {
-  "installCommand": "echo $PWD && ls -al && python3 -m pip install -r requirements.txt",
-  "buildCommand": "echo $PWD && ls -al && ./build.sh",
+  "installCommand": "echo 'Install step PWD:' $PWD && if [ -f requirements.txt ]; then ls -al && python3 -m pip install -r requirements.txt ; else echo 'requirements.txt not found, moving to project root' && cd .. && ls -al && python3 -m pip install -r requirements.txt ; fi",
+  "buildCommand": "echo 'Build step PWD:' $PWD && if [ -f build.sh ]; then ls -al && ./build.sh ; else echo 'build.sh not found in current directory, moving to project root' && cd .. && ls -al && ./build.sh ; fi",
   "outputDirectory": "site"
 }