soroush.asadi
96c8abbeb3
The HTTPS Nexus serves an incomplete cert chain that container trust stores reject (NU1301 PartialChain / UNABLE_TO_GET_ISSUER), failing CI restore/install. - NuGet has no strict-ssl flag → point CI + Dockerfile + compose at the plain-HTTP Nexus (http://171.22.25.73:8081, allowInsecureConnections) — no TLS, no cert check. - npm: add --strict-ssl=false to the CI web-check install (Dockerfile already had it); Docker npm registry default also moved to the HTTP Nexus. - ENV_FILE.example documents NUGET_INDEX/NPM_REGISTRY overrides. Local dev (Windows trusts the cert) + image base pulls (Docker trusts it) are unaffected — only in-container package feeds switch to HTTP. Co-Authored-By: Claude Opus 4.8 <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.