Fix Next.js API route for Amplify WEB_COMPUTE platform

- Add .env.production for Amplify environment variable mapping
- Update artifacts configuration for WEB_COMPUTE platform
- Add explicit nodejs runtime for API route
- Enable serverActions in Next.js config
- Add debugging output for environment variables

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
DaX
2025-06-19 00:38:50 +02:00
parent d5f16af3b3
commit 58d91f78ab
4 changed files with 19 additions and 3 deletions

5
.env.production Normal file
View File

@@ -0,0 +1,5 @@
# This file is for Amplify to know which env vars to expose to Next.js
# The actual values come from Amplify Environment Variables
CONFLUENCE_API_URL=${CONFLUENCE_API_URL}
CONFLUENCE_TOKEN=${CONFLUENCE_TOKEN}
CONFLUENCE_PAGE_ID=${CONFLUENCE_PAGE_ID}

View File

@@ -5,13 +5,19 @@ frontend:
commands:
- npm ci
- npm run security:check
# Print env vars for debugging (without exposing values)
- env | grep CONFLUENCE | sed 's/=.*/=***/'
build:
commands:
- npm run build
artifacts:
baseDirectory: .next
baseDirectory: ./
files:
- '**/*'
- .next/**/*
- node_modules/**/*
- package.json
- next.config.js
- public/**/*
cache:
paths:
- node_modules/**/*

View File

@@ -1,6 +1,8 @@
import { NextResponse } from 'next/server';
import { fetchFromConfluence } from '../../../src/server/confluence';
export const runtime = 'nodejs';
export async function GET() {
try {
// Get environment variables from server-side only

View File

@@ -1,7 +1,10 @@
/** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
// Remove output: 'standalone' for Amplify
// Ensure server-side features are enabled
experimental: {
serverActions: true,
},
}
module.exports = nextConfig