config file railway.json does not exist in the new created environment

I have a project already working with Github and Postgress, I created a new environment from it, but now I can't deploy the project from Github because it keeps giving the error "config file railway.json does not exist", and that it is configured exactly the same as the main environment project.
Solution:
I solved the problem, I simply had to specify the path /backend/railway.json, I didn't know I had to do this because I thought it would get everything I specified in the field above as "/backend"
Jump to solution
30 Replies
Percy
Percy6mo ago
Project ID: 6eca6984-5b4b-40cd-9660-dab7e99f7321
Mario Paglia
Mario Paglia6mo ago
6eca6984-5b4b-40cd-9660-dab7e99f7321
Brody
Brody6mo ago
can you show a screenshot of this error?
Mario Paglia
Mario Paglia6mo ago
@Brody
No description
Mario Paglia
Mario Paglia6mo ago
No description
Brody
Brody6mo ago
where is your railway.json file located
Mario Paglia
Mario Paglia6mo ago
@Brody The project is configured exactly the same as the production environment, but in the development environment that I created it does not work, as it is the same project, the same path but with a new database /backend/railway.json
Brody
Brody6mo ago
what is the root directory set to
Mario Paglia
Mario Paglia6mo ago
This here is the same project running in the production environment, with the same configuration, same commit and same railway.json file
No description
Mario Paglia
Mario Paglia6mo ago
Produtction
No description
Mario Paglia
Mario Paglia6mo ago
Development (new environment)
No description
Brody
Brody6mo ago
do you perhaps have a service variable that's trying to tell railway where a railway.json is?
Mario Paglia
Mario Paglia6mo ago
No description
Brody
Brody6mo ago
well then that's about all the basic debugging steps I can think of, I will have to flag the team
Duchess
Duchess6mo ago
Thread has been flagged to Railway team by @Brody.
Brody
Brody6mo ago
keep in mind it's the weekend, so the team will be getting back to you on a weekday
Mario Paglia
Mario Paglia6mo ago
Thank you very much for your help, I will wait for the support team to respond.
Linear
Linear6mo ago
Issue PRO-1670 created.
Ray
Ray6mo ago
Can you share how you created the environment?
Mario Paglia
Mario Paglia6mo ago
With my main environment already created and the services working, I created a new environment, where he duplicated the github project and created a new database, but this github project cannot find the railway.json file and the two environments this project is configured equally.
jr
jr6mo ago
Hey there, Just want to check if this is still an issue for you? I see that the project now only has a single environment setup
Mario Paglia
Mario Paglia6mo ago
But has anything been done to fix this problem?
jr
jr6mo ago
We are not seeing any other users with this issue and haven't been able to reproduce ourselves. I've still raised to our team but just wanted to first confirm you were up and running
Mario Paglia
Mario Paglia6mo ago
I just created the "development" environment again, I configured all the environment variables, the configuration of the develpopment "back-end" service is the same as the configuration of the production "back-end" service, each one pointing to a database Different postgress, but the "development" environment again has the error of not finding railway.json in my repository https://github.com/mariopaglia/nextjs-structure in the /backend folder
No description
Solution
Mario Paglia
Mario Paglia6mo ago
I solved the problem, I simply had to specify the path /backend/railway.json, I didn't know I had to do this because I thought it would get everything I specified in the field above as "/backend"
Mario Paglia
Mario Paglia6mo ago
No description
jr
jr6mo ago
ahh okay, so previously the config file path was just "railway.json"
Mario Paglia
Mario Paglia6mo ago
Exactly, but as there are different back-end and front-end projects within my repository, I left the railway.json file directly within the /backend folder, I didn't know that I had to specify the path again since I was already in the field above saying it was in the /backend folder
jr
jr6mo ago
Yes that is sure confusing. We can improve that for sure!