Refactor security scanning and database setup
Some checks failed
CI/CD Pipeline / test (push) Successful in 10m54s
Security Scan / security (push) Failing after 5m21s
CI/CD Pipeline / security (push) Successful in 5m25s
CI/CD Pipeline / build (push) Failing after 2m27s
CI/CD Pipeline / deploy (push) Has been skipped

- Update security scan workflow to utilize a dedicated script for checking secrets, improving detection accuracy.
- Modify database connection setup in multiple scripts to use an environment variable fallback for DATABASE_URL, enhancing flexibility in different environments.
This commit is contained in:
2025-09-11 11:17:35 +02:00
parent c4bc27273e
commit f7e0172111
7 changed files with 127 additions and 25 deletions

View File

@@ -12,7 +12,7 @@ console.log('💡 For full development environment with DB, use: npm run dev:ful
const env = {
...process.env,
NODE_ENV: 'development',
DATABASE_URL: 'postgresql://portfolio_user:portfolio_dev_pass@localhost:5432/portfolio_dev?schema=public',
DATABASE_URL: process.env.DATABASE_URL || 'postgresql://portfolio_user:portfolio_dev_pass@localhost:5432/portfolio_dev?schema=public',
REDIS_URL: 'redis://localhost:6379',
NEXT_PUBLIC_BASE_URL: 'http://localhost:3000'
};