You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies in advance for complete beginner React related questions:
You guys just so happen to have done exactly what I was hoping to do: build a grapes.js instance that uses tailwind blocks. Problem is I'm looking to integrate this into a Django backend, and thus don't really want to use Next, I'd rather create the API endpoints that grapes needs in python, and save the grapes state to the existing database.
Would it be possible to separate the grapes.js build in this project from Next entirely and just build the grapes.js bundle alone?
The text was updated successfully, but these errors were encountered:
You have a few options if the end goal is to integrate Destack with Django and your DB.
Leave Next.js for your frontend and fork the project to change the endpoints from localhost at port 3000 to your Django backend. You can read Destack's backend implementation to guide you build your own.
Wait we until we release the React version of this peoject that as a side effect will allow custom backends. Although I look forward to this it might take a while to find the time to work on it.
Build a clone from scratch and take some ideas from our frontend renderer component.
Apologies in advance for complete beginner React related questions:
You guys just so happen to have done exactly what I was hoping to do: build a grapes.js instance that uses tailwind blocks. Problem is I'm looking to integrate this into a Django backend, and thus don't really want to use Next, I'd rather create the API endpoints that grapes needs in python, and save the grapes state to the existing database.
Would it be possible to separate the grapes.js build in this project from Next entirely and just build the grapes.js bundle alone?
The text was updated successfully, but these errors were encountered: