a year ago
My project have this structure
root/
├── client/ (React app)
| ├── .env
| ├── .package.json
| └── src/
├── server/ (Node server)
| ├── .env
| ├── .package.json
| └── src/
└── package.jsonTo run it successfully one have to:
install dependencies for both client and server.
build the client.
start the server
In the root's package.json I have this script to install client and server dependencies:
"install": "npm install --prefix client & npm install --prefix server"In local development this works, dependencies both for client first and then server are installed, although the process doesn't exit on its own, I have to manually press Ctrl-C, but then all the next steps work just fine and I can run the application as expected.
However when deploy it to railway although it installs the dependencies it fails at the next step (build) because it cannot find both react-script and rimraf, which are necessary to run the build script, which leds me to think that it is not installing the dependencies correctly
how can I tell railway to install dependencies for client/ and server/?
0 Replies
a year ago
are you able to share the repo?
sure it is a public repo, https://github.com/GhostOrder28/inmobitas
a year ago
do the client and server import stuff from one another?
no imports, just the build script in the client's package.json removes and creates a directory in server
a year ago
so the server serves the client app?
yep, client basically just build the frontend files into a public/ dir that is located inside server/ and then the server can serve those static files
a year ago
interesting approach
a year ago
can you send me your latest build logs please -
well before I had both on separated repos, but then I always ended duplicating the commit messages for both, since every change in the client repo forces also an update in the server repo because it serves the static files generated by create-react-app in client xD
a year ago
interesting in that the server is serving the client, not that you have both apps in one repo because that part is normal. in my experience its best to have the client (or frontend) serve itself and the backend serve itself (for lack of a better term)
a year ago
try adding a nixpacks.toml to your project with this in it -
[phases.install]
cmds = ['npm run install']a year ago
new build logs please
a year ago
then i might recommend moving to npm workspaces, it would help here
a year ago
haha that too
I don't know why but I just completely forgot that the client having its own little sever to serve just the build files is a thing xD
a year ago
and thats easily achievable with the nixpacks.toml and Caddyfile from this repo
oh, I was thinking in creating a barebones nodejs server inside the client and serve the build files through it
a year ago
thats also not ideal
a year ago
its best to use a web server as a web server, and node for node stuff
a year ago
you would only need to read about it if you want to learn more, those two files are drag and drop
yep, I always try to know understand at least the basics of the technology I use in my apps so I can customize it when I needed or have some notion of where to look at
a year ago
love that attitude
a year ago
for sure