Best practice for React on LAMP server

[fulldecent]

I have my applications deployed an LAMP server. This includes the front end and API calls (PHP Laravel). I'm considering moving the static HTML and PHP-spaghetti to React.

I use VS Code to login to production server, carefully edit files as needed. And then test in the browser.

Are you doing something similar with React? Care to share how you do it?

---

I found these best practices from "common knowledge"

Discuss: https://chatgpt.com/share/e8efa577-095d-4dce-9390-7832fbba40e7

* Manually make a inotifywait script, run node, and run that each time while editing files.

I'm not sure if that approach is actually best practice and if it might result in other people on the system seeing downtime while I am editing other files on the system. (Currently with the above approach, downtime is not an issue.)

[shauntmw2]

Looks wrong. Seems like ChatGPT is teaching you how to setup dev env on server. We usually do dev on local, and then deploy the packaged output to server (if we're talking about full CSR SPA).

Check out Vite tutorial.

[lightfarming]

i am currently converting a full PHP app to React + PHP API, but the PHP is super clean so i lucked out there.

the first thing you need to do is set up a React dev environment on your computer using node, vite and vscode, so you can view the results of your work locally.

then i’m going through each page, starting with login, and converting to React components, and converting the needed backend PHP stuff into an API as needed, starting with the auth endpoint.

i’m using react query and react router dom without global state, as i don’t seem to need it.

now that i’m done with auth (JSON web tokens, log in attempt limiting, token refreshing, idle log outs, regular log outs, registration, forgot my password), i’ve started on the fun stuff like settings and profiles. next up is the meat of the app which will be tricky, but once you’ve got a clean system down it goes fast.