I'm experiencing an issue with my Node.js Express backend where the application doesn't seem to detect Supabase credentials, even though they're set in the Railway dashboard and I've also tried implementing a fallback with hardcoded credentials in the start.sh script. The logs consistently show "SUPABASE_URL defined: NO" regardless of the approach used, which suggests there might be something unique about how environment variables are being handled in this particular deployment. All other aspects of the application are working well, and I'd appreciate any insights on what might be preventing the Supabase environment variables from being properly accessed by the Node.js process.