YesBackend eka rest api ekak widiyata gahapan.
React kathawak adala na backend ekata.
Wenam github repo ekaka dapan.
Frontend eken rest api eka call karapan. (fetch use karapan, axios danna epa den use karanne na wediya)
Wenama repo ekaka dapan.
This is controversial, if the back end is going to be reused by multiple frontends, then it might be okay to have it in a separate repo, but if the backend solely used by the react frontend, you can have both in the same repository. this approach called Mono repo (All the sub components in the same project contains in a single repo) Advantage is, you just need to clone a single repo which contain full source code to get the system up and running.Wenama repo ekaka dapan.
Backend eka rest api ekak widiyata gahapan.
React kathawak adala na backend ekata.
Wenam github repo ekaka dapan.
Frontend eken rest api eka call karapan. (fetch use karapan, axios danna epa den use karanne na wediya)
Wenama repo ekaka dapan.
Laravel asse gahanne kohomda bn
Laravel kiyanne server side render wena ekak ne..react eka client eka.
Hodama de wena wenama gahapan, Laravel api and react front end app eka
mehema neda 1 main folder ek athule me deka tiyenne
LARAVEL INERTIA REACT or VUE , kiyala tiyanawa..pattama lesi ..mara handy...plug and play wage....
------ Post added on Jan 3, 2024 at 10:22 AM
meka karala balanawa![]()
not directly related to OP's questionYes
build the backend as a REST service and write a react frontend to consume the rest API.
This is controversial, if the back end is going to be reused by multiple frontends, then it might be okay to have it in a separate repo, but if the backend solely used by the react frontend, you can have both in the same repository. this approach called Mono repo (All the sub components in the same project contains in a single repo) Advantage is, you just need to clone a single repo which contain full source code to get the system up and running.
something like this
repository
├── frontend
└── backend