Fix Amplify environment variable configuration

- Add amplify.yml for proper build configuration
- Update next.config.ts to expose YOUTUBE_API_KEY env var
- This should fix the issue with secrets not being available in production

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Derek Slenk 2025-06-27 14:56:31 -04:00
parent ddbd6c27d6
commit 40c2f0c263
13 changed files with 47206 additions and 47183 deletions

20
amplify.yml Normal file
View file

@ -0,0 +1,20 @@
version: 1
frontend:
phases:
preBuild:
commands:
- npm ci
build:
commands:
- env | grep YOUTUBE_API_KEY || echo "YOUTUBE_API_KEY not found in environment"
- npm run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- node_modules/**/*
- .next/cache/**/*
buildPath: /
appRoot: /

View file

@ -24,6 +24,9 @@ const nextConfig: NextConfig = {
},
],
},
env: {
YOUTUBE_API_KEY: process.env.YOUTUBE_API_KEY || '',
},
};
export default nextConfig;