2 months ago
I set up a project which has multiple services, and then initially I set it up with a staging environment connected to a GitHub repo, and I deployed everything. When I was happy with it, then I created a new environment for production, and I just cloned the staging environment to have the production set up.
Now, after the app has been live for about a couple of weeks, I wanted another service, so I went back to the staging environment and added a new service which is connected to a GitHub repo. I called this the admin UI service. When I was happy with the staging testing, now I want to promote this service to production, and I don't know how.
I went to the production environment. I activated the production environment, and I tried to recreate the service again by connecting from GitHub. When I tried to use the same name for the service that was being used in the staging, then I see the error that it is not allowed because there is already a different service in this project with the same name. How to solve this problem?
The error I see is as follows:
Error: Updating service name
A service named "Admin UI" already exists in this project
So it is correct that the Admin UI service exists in the project, but it exists in the staging environment, and now I want it in the production environment. I could choose a different name, and it would work, but I want to know why all my other services have the same names and they are fine, but this one is complaining about it.
Pinned Solution
2 months ago
hey sambhav,
you don't need to recreate the service manually. railway has a sync feature for exactly this. go to your production environment, click "sync" at the top of the canvas, select staging as the source, your admin ui service will appear tagged as "new", review the staged changes and hit deploy. done.
5 Replies
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 2 months ago
2 months ago
For now, I just selected a different name because I was kind of blocked and I need the deployment to go through, but it is interesting that I cannot rename it to the same name that exists in staging.
2 months ago
hey sambhav,
you don't need to recreate the service manually. railway has a sync feature for exactly this. go to your production environment, click "sync" at the top of the canvas, select staging as the source, your admin ui service will appear tagged as "new", review the staged changes and hit deploy. done.
2 months ago
When you select the environment, this is available on top.
Attachments
2 months ago
Oh, Nice. Didn't know about that. I saw the sync button but I am always afraid to click on it because I don't know what it is going to sync. but now I know.
Railway if you are watching, it would be worth to add a tooltip on that button to say what it is going to do.
sambhav-gore
Oh, Nice. Didn't know about that. I saw the sync button but I am always afraid to click on it because I don't know what it is going to sync. but now I know. Railway if you are watching, it would be worth to add a tooltip on that button to say what it is going to do.
2 months ago
yeah totally, the sync button could use a tooltip for sure. glad it helped
Status changed to Solved chandrika • 2 months ago