Merging Projects
With the new Group features for the services dashboard I am trying to Merge all my Railway Projects into a single Project and group each projects services with the new feature added.
I wanna know if this is a good idea, considering this will make the project size huge and I'm worried about behind the scenes stuff on railway handling all of this
Solution:Jump to solution
no, merging all your projects is not a good idea.
a single project should only contain the services that are needed for that specific project.
no, each service can use up to the allowed resources....
12 Replies
Project ID:
N/AN/A
also is 1 project = 1 PC server?
if yes, does it mean merging projects means sharing CPU & RAM across all services in it?
Solution
no, merging all your projects is not a good idea.
a single project should only contain the services that are needed for that specific project.
no, each service can use up to the allowed resources.
Ah okay, we have some services that are duplicated across projects and think that if we can just merge them into one big project we can avoid redeploying the same services in each project or having to deal with egress fees if we seperate those services
if they are actually different projects then you should keep them as such
aight thanks for clarifications!
no problem!
@Brody what if each project has at least one service to be shared to another project.
i understand what you mean, we can share it to different project, but it will cost egress fee.
now that we have "Group" feature, we plan to merge it into one. could you please let us know what might be the risk or the caveats of having those projects merged into a single project? thanks in advance Brody!
if you have services spread out across multiple projects that are communicating with one another then yes you would want to merge them into a single project so that you can use the private network
@Brody thanks a lot for your input
no problem!