-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Implement next.js (Alongside existing frontend) #1733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…el loading and inference
… client generation
…ges to generate a commit message.
…thentication layout
…ironment variables
…nvironment variables
…ocker-compose.yml
…nment configurations
Hello @athrael-soju, thanks for taking the time to contribute. For now, we don't intend to migrate to Next.js. For future contributions, it might be helpful to start by opening a discussion with your ideas, just to make sure they're aligned with the project's direction before you invest too much time working on them. We appreciate the effort, but we'll be passing on it for now. Thanks again! 🙏 |
@athrael-soju this looks beautiful. Is this available in some repo and branch on your profile? |
Thanks. I have something similar I still support, but it includes a visual model for knoweledge retrieval: https://github.com/athrael-soju/fastapi-nextjs-colpali-template If you're looking for something with just next.js and fast API, your best bet is likely: https://github.com/vintasoftware/nextjs-fastapi-template |
Summary
Introduction of a completely functional Next.js Template (alongside the existing frontend) including:
And as highly requested:
TODO:
Feature
)HOW TO:
frontent-next.js
as you did withfrontent
to generate the client scripts, set environment variables and so on.Related Issue: Issue: #1394
Enjoy and if you want to help finalize the deployment/documentation I'd greatly appreciate it!