2 years ago
I don't know what's happening that won't let me deploy my server
0 Replies
2 years ago
you have your Google client id and key in a .env file in a public repo, please go and re-generate them
2 years ago
after that's done we will tackle deploying both frontend and backend onto railway properly
2 years ago
okay whatever works for you
2 years ago
can you show me a screenshot of your railway project just so I know what we are working with
2 years ago
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
2 years ago
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
2 years ago
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
2 years ago
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
2 years ago
remove the PORT variable, not sure whats thats doing there
2 years ago
can you explain your start script to me?npm run server && npm run api
2 years ago
it should just be node index.js
It was an old code and I left it as it was and added that last bit to test if it worked
2 years ago
okay, please make the change i suggested
2 years ago
remove the start command you have set in the service settings please
2 years ago
set the root directory to /server
2 years ago
deploy the changes
[Region: us-west1]
==============
Using Nixpacks
==============
context: 4a43c7f96e3e643f43d3cf9b92568d73
Nixpacks build failed
╔════════ Nixpacks v1.21.2 ═══════╗
║ setup │ nodejs18, npm-9x ║
║─────────────────────────────────║
║ start │ ║
╚═════════════════════════════════╝
Error: No start command could be found
2 years ago
retake this screenshot please
2 years ago
also, going forward, always use this to send logs please
2 years ago
not quite the same screenshot
2 years ago
you have not yet set a root directory
2 years ago
please do that
2 years ago
I think you set a watch path? please undo that, you need to set a root directory
2 years ago
retake this screenshot please
2 years ago
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.js
Model 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.
2 years ago
that warning?
2 years ago
it's truly of no concern
Thank you very much, if it weren't for your help I would have gone bald from stress
2 years ago
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
2 years ago
okay after dinner
If you want, send me the request and write to me privately when you are ready.
2 years ago
rename that failed service to something that relates to your frontend, it is going to be the frontend service now
2 years ago
and then a screenshot of when thats done please
2 years ago
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
2 years ago
heck no, we shill railway here
2 years ago
theres ways to do nearly everything, so lets get railway to run a production grade server instead
2 years ago
first off, do you have any start or build commands set in the frontend service?
2 years ago
that is correct, we just have to have a way to serve those files, and we will do so like this
copy the nixpacks.toml and Caddyfile from this repo into your client folder
2 years ago
client
2 years ago
push the changes
2 years ago
let me know if something goes wrong
2 years ago
open it up
2 years ago
haha i meant open the frontend's domain
2 years ago
working now?
2 years ago
send the link please
2 years ago
it works?
2 years ago
great!