does your repo happen to be public?
if not would it be possible to just provide a screenshot of the root level of the repo?

I believe it is private. Does it need to be public? Here is a screenshot of the upload error

it doesnt need to be public, I was asking because I wanted to take a look at your project structure
this is because the project structure is relevant to that error

Repo root

I just explained this to someone in another thread an hour or so ago so I'm going to copy-paste that explanation here:

When you deploy something on a container-like service (such as Railway) it needs what's known as an image to deploy. You can provide an image directly or provide a file called "Dockerfile" which explains how to build the image for your service.

Railway built a service called Nixpacks which can build that Dockerfile for you automatically, but has deprecated that service for their new service called "Railpack" which builds the image directly. It does this by looking at your app's structure, its files and such to understand what image needs to be built for your app.

The issue is that it uses set rules to follow and when your app does not use standardized naming conventions or file structures then Railpack simply doesn't know how to build your application image. That's the error you're seeing there.

I thought as much, thank you

My guess is you linked the MACQ_CRM directly, meaning your actual project root that Railpack sees is:

• backend

• frontend

it cant know how to build your app from that. Typical issue in monorepos. There's 2 ways you can go about solving this:

• Automatic (beta): Railway just introduced a feature that'll automatically configure your app using AI. I believe to trigger it you simply need to create a Project directly from a GitHub repo. Meaning go to , click on GitHub Repository and select your repo. If I'm right then this should automatically create 2 services for you. Make sure you have the Magic Config flag enabled in though

• Manual (recommended): You have a monorepo setup, for that to work on Railway you need to break it into its respective services. You'll need to deploy 2 services: one for your backend and one for your frontend. Just create 2 services, linking the same github repo, then in service settings click Add Root Directory and select backend for one and frontend for the other. Then configure as you would otherwise.

Thanks so much!

Of course 🙂