React + Laravel

Psiko

Well-known member
  • Mar 10, 2023
    4,609
    4,404
    113
    Arituza
    Frontend React and Backend Laravel Project karala tiynwd?


    ekama project eke react wenama , laravel wenama karana ekada hoda?


    nattan laravel athule react liyana ekada honda?


    crud ekk gahnne .
     
    Last edited:

    Software_Eng

    Well-known member
  • Dec 15, 2017
    1,137
    1,188
    113
    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.
     

    NEMISIS

    Well-known member
  • Nov 13, 2013
    9,385
    15,102
    113
    Colombo
    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.
    Yes
    build the backend as a REST service and write a react frontend to consume the rest API.

    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.
    something like this

    repository
    ├── frontend
    └── backend
     

    geeko

    Well-known member
  • Mar 18, 2013
    6,464
    3,285
    113
    kalekata kalin man wadak patan gaththa magema project ekak. react valin lassanata front end eka gaththa. backend eka laravel karanna kiyala thamai hithagena hitiye. habai a vade magin nawathuna. laravel igena gannath ekka thamai vade karagena giye
     

    YasiBabi

    Member
    Feb 4, 2023
    6
    7
    3
    Laravel eka athulema react build karanna. project 2k maintaince karanawada wada eka lesi. api calls walin data ganna. passport hari JWT walin wage authentication use karanna
     
    • Like
    Reactions: B.Chat and Psiko

    Psiko

    Well-known member
  • Mar 10, 2023
    4,609
    4,404
    113
    Arituza
    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
     
    • Like
    Reactions: B.Chat

    Draco Malfoy

    Well-known member
  • Feb 9, 2019
    6,503
    13,403
    113
    Malfoy Manor, Wiltshire, England.
    Yes
    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
    not directly related to OP's question
    but
    api kohomada hadana software ekaka (eg: billing system of a pastry shop network like P&S, large system like food city cashiering system) REST API thiyena monolith or REST api Micro service yanawada da kiyala decide karanne?
     
    • Like
    Reactions: B.Chat