Files
portfolio/app/api/fetchProject/route.tsx
Denshooter b87b1d6237 refactor: use environment variable for GHOST_API_KEY
Replace hardcoded GHOST_API_KEY with process.env.GHOST_API_KEY in 
API routes to enhance security. Update Docker commands in the CI 
workflow to pass the GHOST_API_KEY as an environment variable. 
Add GHOST_API_KEY to the Next.js configuration for consistent 
access across the application.
2025-02-12 17:30:31 +01:00

33 lines
941 B
TypeScript

import { NextResponse } from "next/server";
export const runtime = "nodejs"; // Force Node runtime
const GHOST_API_URL = "http://192.168.179.31:2368";
const GHOST_API_KEY = process.env.GHOST_API_KEY;
export async function GET(request: Request) {
const { searchParams } = new URL(request.url);
const slug = searchParams.get("slug");
if (!slug) {
return NextResponse.json({ error: "Slug is required" }, { status: 400 });
}
try {
const response = await fetch(
`${GHOST_API_URL}/ghost/api/content/posts/slug/${slug}/?key=${GHOST_API_KEY}`,
);
if (!response.ok) {
throw new Error(`Failed to fetch post: ${response.statusText}`);
}
const post = await response.json();
return NextResponse.json(post);
} catch (error) {
console.error("Failed to fetch post from Ghost:", error);
return NextResponse.json(
{ error: "Failed to fetch project" },
{ status: 500 },
);
}
}