Fix Amplify environment variable access
- Simplified amplify.yml to export env var during build - Updated both gallery and dadvocate pages to check multiple env var names - Added debugging to show available env vars - Added publicRuntimeConfig and serverRuntimeConfig to next.config.ts - Created config helper in lib/config.ts 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
2de4fb5f69
commit
06a0051c51
5 changed files with 29 additions and 30 deletions
|
@ -24,6 +24,14 @@ const nextConfig: NextConfig = {
|
|||
},
|
||||
],
|
||||
},
|
||||
// Make environment variables available to the browser
|
||||
publicRuntimeConfig: {
|
||||
YOUTUBE_API_KEY: process.env.YOUTUBE_API_KEY,
|
||||
},
|
||||
// Server-side environment variables
|
||||
serverRuntimeConfig: {
|
||||
YOUTUBE_API_KEY: process.env.YOUTUBE_API_KEY,
|
||||
},
|
||||
};
|
||||
|
||||
export default nextConfig;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue