mirror of
https://github.com/QuivrHQ/quivr.git
synced 2024-12-14 17:03:29 +03:00
71d4a63a17
# Description Currently, the production Docker images are very large, sitting at 4.17 GB for the frontend image, and 3.49 GB for backend images. This change adds multi-stage builds, to optimize the image sizes, which results in the following improvements: - frontend image size: 4.17 GB -> 1.64 GB - backend image size: 3.49 GB -> 1.71 GB I hope this is appropriate as there is no open issue for this that I know of. I implemented this change and tested it locally, and would be glad to discuss this and open an issue if necessary. ## Checklist before requesting a review Please delete options that are not relevant. - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented hard-to-understand areas - [x] New and existing unit tests pass locally with my changes ## Screenshots (if appropriate): Image sizes before: <img width="1416" alt="image" src="https://github.com/StanGirard/quivr/assets/8296549/fcbb020f-8165-4549-ae30-823318691ec6"> Image sizes after: <img width="1416" alt="image" src="https://github.com/StanGirard/quivr/assets/8296549/d3f43c78-be26-4c38-9d23-9c1b0e9e37f2"> |
||
---|---|---|
.. | ||
app | ||
e2e | ||
lib | ||
pages/blog | ||
public | ||
services/analytics | ||
shared | ||
styles | ||
.dockerignore | ||
.eslintrc.js | ||
.gitignore | ||
.lintstagedrc.js | ||
Dockerfile | ||
Dockerfile.dev | ||
globals.css | ||
middleware.ts | ||
next-sitemap.config.js | ||
next.config.js | ||
package.json | ||
playwright.config.ts | ||
pnpm-lock.yaml | ||
postcss.config.js | ||
README.md | ||
sentry.client.config.ts | ||
sentry.edge.config.ts | ||
sentry.server.config.ts | ||
tailwind.config.js | ||
tsconfig.eslint.json | ||
tsconfig.json | ||
vitest.config.ts | ||
vitest.setup.ts | ||
yarn.lock |
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
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 Inter, a custom Google Font.
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.