Installing dependencies for sub directories
My project have this structure
To run it successfully one have to:
1. install dependencies for both client and server.
2. build the client.
3. start the server
In the root's
package.json I have this script to install client and server dependencies:
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/?31 Replies
Project ID:
80b7a72a-2271-48a0-8bc9-a5758f24c84780b7a72a-2271-48a0-8bc9-a5758f24c847
are you able to share the repo?
sure it is a public repo, https://github.com/GhostOrder28/inmobitas
GitHub
GitHub - GhostOrder28/inmobitas: New repo for my real estate manage...
New repo for my real estate manager project, it combines both client and server codebases to a more convenient deployment - GhostOrder28/inmobitas
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
serverso 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 filesinteresting approach
can you send me your latest build logs please - https://bookmarklets.up.railway.app/log-downloader/
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
sure let me check the link
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)
oh mmm, yeah certainly that's another common approach
try adding a nixpacks.toml to your project with this in it -
ok
it failed again with the same error, rimraf and react-scripts not found
new build logs please
oh right, sorry
then i might recommend moving to npm workspaces, it would help here
I see, well thank you for your time brody, I will read more about that
or maybe I just go with the more common approach you mentioned 😅
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
and thats easily achievable with the nixpacks.toml and Caddyfile from this repo
https://github.com/brody192/create-react-app-starter
oh, I was thinking in creating a barebones nodejs server inside the client and serve the build files through it
thats also not ideal
its best to use a web server as a web server, and node for node stuff
well that's right
I will read more on nix and cady, thank you
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
but having an easy quick start helps
love that attitude
hehe, I guess being self taught helped to build it
for sure