One environment per customer
My application is in Finance and I require a separate server operating for each individual customer. Each of these server are derived from exactly the same codebase. My question is regarding how this is best setup in Railway, I can see two options;
1. Duplicate each project, one for each customers (given templates aren't available for private repo's this isn't ideal)
2. Create one environment for each customers, what are the implications here? Any reason why this would be a bad idea?
Thanks!
PS; what's happening in the backend for #2, is it simply launching a new process of the same image?
4 Replies
i don't know if railway is the best fit for something like that
you might look into a container orchestrator like kubernetes or nomad but idk
@Charles_ - this sounds perfect for our Teams plan and the API
Going to tag in @farazpatankar to gather more info on your usecase
Thanks @Angelo - would you mind explaining why multiple environments might not be the best for this use case?
I will be upgrading to teams but I just want to make sure I understand correctly
Note that my customer count is relatively low (<100) but each is high-value
If you can do multiple projects (via the API), isn't that just better in terms of separation? It gives you a lot more room for flexibility in the future.