Arnaud
d035378520
Dockerfile still COPYed packages/api-types (deleted in the prior audit-fixes commit), breaking Portainer builds. Also drop apps/web/middleware.ts, added in the same commit for auth guarding — it duplicated and conflicted with the pre-existing apps/web/proxy.ts (Next 16's middleware entry point), which already redirects unauthenticated requests to /login, 401s API routes, and covers /recipes/new, /explore, /search, /settings/webhooks/docs via its catch-all matcher. Having both middleware.ts and proxy.ts breaks `next build` outright. Verified with a local `docker build` end to end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.