Agree with this

Hey Jim, this is one of our most requested asks. We aren't entirely sure how to best support this use case but wanna let you know that we are thinking about it!

Hey Jim, this is one of our most requested asks. We aren't entirely sure how to best support this use case but wanna let you know that we are thinking about it!

Angelo Saraceno: Probably worth noting I didn't actually end up needing it for Vapor, since you support postgres and redis but it probably would make a lot of people's lives easier to have compose support. I'm glad you're taking the time to think about how it should integrate into your product instead of half-assing it though. :)

Analyzing docker-compose file and creating services would be cool.

This feature will really make life easier for a lot of engineers. Amazing work you guys are doing

We are looking into having a system that can map compose.yml(s) into Railway IaC and then you can run your project from Railway. Not on the near term roadmap but now since we have the primitives, it's possible. Stay tuned.

Angelo Saraceno: this would be helpful

We are looking into having a system that can map compose.yml(s) into Railway IaC and then you can run your project from Railway. Not on the near term roadmap but now since we have the primitives, it's possible. Stay tuned.

Angelo Saraceno: how about now ?

any update on this? ive been waiting for ages to migrate all of my products that rely on docker compose from a vps to railway, but this is the only thing stopping me.

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

Angelo Saraceno: Will this work for testing purposes? it would be great to be able to roll a n8n instance with a postgresdb in Railway: https://github.com/n8n-io/n8n/blob/master/docker/compose/withPostgres/docker-compose.yml

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

Angelo Saraceno: https://docs.directus.io/self-hosted/docker-guide.html#example-docker-compose

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

Angelo Saraceno:

supabase!

https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml

guide: https://supabase.com/docs/guides/self-hosting/docker

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

Angelo Saraceno: https://github.com/SnailyCAD/snaily-cadv4/blob/main/docker-compose.yml

this is for the service im going to transfer from my vps to railway. hopefully you can get everything on here supported

I really really really like this feature

So this was my hackathon project and I whipped up a proof of concept- we can't support everything within the compose spec (https://github.com/compose-spec/compose-spec/blob/master/spec.md) but we can get it so that PORTs and Volumes are provisioned.

My question to the community is, can you provide some sample docker-compose.ymls that we can test against to make sure that we support what you expect?

Angelo Saraceno:
https://raw.githubusercontent.com/standardnotes/server/main/docker-compose.example.yml

Guide: https://standardnotes.com/help/self-hosting/docker

Any progress? Really looking forward to this feature

Railway would need to support more infrastructure-related stuff, like multiple volumes per service and sharing volumes across services before they could support the docker-compose file that you have linked, so support is a long way out

This is still good, this is going to be my weekend project. We have one last pass on the environment work that we wanna do- this means that when we have envs with super complex deploys with multi service : one volume deployment, we are ready.

It's like driving a shipping tanker- turning now means we are aligned in three months.

Largest request from this user was compose support

https://x.com/iamalexfranz/status/1758764487606161452?s=46&t=00dq48d1c_GjD9m8fXEJ8w

Would love an update on this. I need to be able to deploy a Directus image with custom extensions and I require docker compose.

That wouldn't require docker compose, this template supports installing extensions out of the box and most importantly it's of far more quality then one you'd get from a docker compose file -

https://railway.app/template/2fy758

Thanks. I already tried this and couldn’t see how I could deploy my own custom extensions without going through the store publishing process, which I’d rather not do.

Can you elaborate on why this is a higher quality?

The template doesn't hardcode anything and has health checks, auto secret generation, variable references, support for installing extensions, and local storage. Just to name a few, it also has a very active community member behind it!

A docker-compose file will never come close in terms of quality to a properly hand-crafted template / project.

If you wanted to open a new help post I'd be happy to help you try to run your directus install on Railway properly!

Any updates on the status of this new feature? I'm trying to deploy a Dify.ai application, it uses Docker Compose. There is no template for this really cool Open Source ai application.

Compose is supported in our new template composer at https://railway.app/compose, but not for projects.

Note that complex docker-compose setups will not work with the above.

Tried it but couln't make it work, it tells me that .yaml are not supported. Would love to see two Open Source AI app development projects on here as easy templates to deploy: Dify.ai (https://github.com/langgenius/dify) and Tasking AI (https://github.com/TaskingAI/TaskingAI). I'm not a software developer or engineer, just a normal person trying to put these apps online for my company. Thank you anyway.

I'm evaluating Railway and this is the first problem I hit given how limited the CLI and config as code are. For me any serious usage of your service is bound to being able to reproduce the environment easily and not through UI & clicks which can be forgotten or mistakenly done. also looking at this 2 years old feature request where the employee says (2 years ago) "this is one of our most requested asks" and is still not having any sign of progress is very concerning.