problems with deploy
I don't know what's happening that won't let me deploy my server
75 Replies
Project ID:
N/AGitHub
GitHub - MiguelSc66/VS-Proyect
Contribute to MiguelSc66/VS-Proyect development by creating an account on GitHub.
you have your Google client id and key in a .env file in a public repo, please go and re-generate them
after that's done we will tackle deploying both frontend and backend onto railway properly
delete them, they are useless
okay whatever works for you
can you show me a screenshot of your railway project just so I know what we are working with
Yes, do you need the project configuration in railway?
a screenshot will suffice for right now, I'll of course have more questions as we go
I have the start command in npm run start, the build command is empty, and the path is server
I have two because I was trying various things in different
two is needed because you have both a backend and a frontend
Yes, but the front is the least important thing, the important thing is the backend and the database
because the only thing I can't connect now is that
fair enough, but there are some very big pitfalls people (including you) will run into when deploying the frontend how you have it currently, but yes let's do the backend first
do you have all the needed database variables setup on the service?
Before I had everything set up, but I accidentally deleted the railwey server and I don't remember how to configure it, that's why I have this problem now haha
yes, PORT y DB_DEPLOY
DB_DEPLOY = URL
remove the PORT variable, not sure whats thats doing there
ok
can you explain your start script to me?
npm run server && npm run api
it should just be node index.jsIt was an old code and I left it as it was and added that last bit to test if it worked
that they recommend that you accommodate
okay, please make the change i suggested
ready
remove the start command you have set in the service settings please
ready
set the root directory to
/serverready
deploy the changes
[Region: us-west1]
==============
Using Nixpacks
==============
context: 4a43c7f96e3e643f43d3cf9b92568d73
Nixpacks build failed
╔════════ Nixpacks v1.21.2 ═══════╗
║ setup │ nodejs_18, npm-9_x ║
║─────────────────────────────────║
║ start │ ║
╚═════════════════════════════════╝
Error: No start command could be found
retake this screenshot please
also, going forward, always use this to send logs please https://bookmarklets.up.railway.app/log-downloader/
not quite the same screenshot
you have not yet set a root directory
please do that
I think you set a watch path? please undo that, you need to set a root directory
ready
retake this screenshot please
okay looks like it's deploying
Thank you very much, everything works again, I have a question about this:
npm WARN config production Use
--omit=dev instead.
server@1.0.0 start
node index.jsModel loaded: Model loaded: Model loaded: Model loaded: Model loaded: Associations defined. Server listening on port: 5849 Everything is fine, it's just that, but I want to know if it could become a problem later on. it would be the npm thing
that warning?
it's truly of no concern
Thank you very much, if it weren't for your help I would have gone bald from stress
jaja
well we still need to do the frontend, because as it stands, you're about to deploy a development server, that's going to be costly and have terrible performance
okay, let's check it
okay after dinner
Okey perfect
If you want, send me the request and write to me privately when you are ready.
but mention me and I will come
rename that failed service to something that relates to your frontend, it is going to be the frontend service now
okey
and then a screenshot of when thats done please
But does railwey serve to build a front end?
you are skipping steps here, railway does not serve anything itself, railway is going to run your start script, and your start script starts a development server
do we use vercel?
heck no, we shill railway here
sorry
theres ways to do nearly everything, so lets get railway to run a production grade server instead
first off, do you have any start or build commands set in the frontend service?
I think if npm run build, it compiles everything with webpack
that is correct, we just have to have a way to serve those files, and we will do so like this
https://github.com/brody192/create-react-app-starter
copy the nixpacks.toml and Caddyfile from this repo into your client folder
Client or Server?
client
ready
push the changes
ready
let me know if something goes wrong
okey
I think everything turned out well
open it up
haha i meant open the frontend's domain
working now?
the console shows that, but the link doesn't show anything
send the link please
React App
Web site created using create-react-app
it works?
now yes
haha
great!