7 months ago
How to retrieve my project Id in Railway web UI platform?
10 Replies
7 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 7 months ago
Status changed to Solved brody • 7 months ago
angelo-railway
CMD+K -> Project+ID or in the url of your Railway Project
7 months ago
not work for me for CMD+K ..... May I know which menu and button I should click to get from UI side. CLI is not work for me. tried tons of times not work for CLI.
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
You can also copy the project Id from the url.https://railway.com/project/<project-id>/
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
Is the project ID same of service Id?
I only have one project, and two services , why I got two different project Id from URL?
Could you clarify with this?
Status changed to Awaiting Railway Response Railway • 7 months ago
Status changed to Awaiting User Response Railway • 7 months ago
david
The screenshots provided show 2 different projects
7 months ago
ok, so that's mean the projects concept is same of the service right? But why I can't delete it? how should I deploy my custom code to railway via website(NOT the CLI, because Your CLI have a lot of bug, I can't use it. but seems like your Web site also have some bugs)
david
The screenshots provided show 2 different projects
7 months ago
Thanks, so that's mean the projects concept is same of the service right? But why I can't delete it? how should I deploy my custom code to railway via website(NOT the CLI, because Your CLI have a lot of bug, I can't use it. but seems like your Web site also have some bugs)
7 months ago
Hello,
There are no bugs here, but I agree this is very confusing.
Your Workspace role is set to Deployer - This means, despite its name, you cannot deploy Via the Web UI or CLI.
This role only allows pushes to GitHub to automatically be deployed without needing to get a team member's approval every time.
If you want to deploy from the Web UI or CLI you will need to ask debbie to make you a Workspace Admin.
As for your question, projects are services are two very different constructs, while all Ids used on the platform are UUIDs, no two Ids are the same.
I recommend checking out the basics docs page to familiarise yourself with the platform a little -
https://docs.railway.com/overview/the-basics
Best,
Brody
brody
Hello,There are no bugs here, but I agree this is very confusing.Your Workspace role is set to Deployer - This means, despite its name, you cannot deploy Via the Web UI or CLI. This role only allows pushes to GitHub to automatically be deployed without needing to get a team member's approval every time.If you want to deploy from the Web UI or CLI you will need to ask debbie to make you a Workspace Admin.As for your question, projects are services are two very different constructs, while all Ids used on the platform are UUIDs, no two Ids are the same.I recommend checking out the basics docs page to familiarise yourself with the platform a little -https://docs.railway.com/overview/the-basicsBest,Brody
7 months ago
Thank you, you're right.
I'd like to understand why the Deployer role does not include deployment permissions. Could you clarify the exact permissions associated with the Deployer role?
It seems counterintuitive for a 'Deployer' role to have limited permissions—only allowing checks, views, and reads, but no write access, and even restricting log visibility. Given the advanced nature of the platform, this seems like an unusual design choice. Could you explain the rationale behind this? Perhaps there's a reason I'm overlooking.Could you explain the logic behind this limited scope?Could you clarify the intended functionality?
This really smart platform as I know. Maybe Apple and Google, Microsoft they should follow your Guide to leader the world techs