Nixpacks is a service that takes a code-base and tries to build a docker image for it which can then be used to deploy your application, unfortunately Nixpacks is made up of algorithms and code rather than magic, and can only use hints within your codebase to understand how to build your application.

Sometimes applications are misconfigured or extremely complex which makes it impossible for Nixpacks to understand how to build your application. What kind of error is Nixpacks giving you? Perhaps it's an easy solution

Nixpacks build failed

Nixpacks was unable to generate a build plan for this app. Error

Your build failed as we could not generate a build plan for your app. This usually happens when using a monorepo and/or setting an incorrect root directory.

Please check the documentation for supported languages: https://nixpacks.com

The contents of the app directory are:

Server/

README.md

Client/

Nixpacks' error called out your problem perfectly: "This usually happens when using a monorepo and/or setting an incorrect root directory"

It looks like you're trying to deploy a mono-repo meaning you just have to correct the root directory for each service.

You'll want to create two services, one for Client and one for Server, each pointing to your GitHub repo. Then in the service settings you'll find an option to "Add Root Directory", you'll want to set the root directory to Client on the client service and Server on the server service.

If you're having trouble, Railway has a very detailed docs page about this exact scenario here: https://docs.railway.com/tutorials/deploying-a-monorepo

EDIT: Heads up, I'm going to bed - I'll check back on this thread when I wake up though

thank you for the information. Also, if my localhost is 5555 for Cilent and for Server is port=4000, when generating a domain for both services, is port 4000 the public domain for Client and Server? or Client will 5555 and Server will be 4000? I'm a bit confused, could you please clarify this for me?

client is likely port 5555 and server is likely port 4000

Also for adding variables, `VITE_BACKEND_HOST=${{Backend.RAILWAY_PUBLIC_DOMAIN}}` do we need to copy and paste this code or we need to replace it with the ports number? I'm confused

Well assuming your backend service's name is Backend and your website uses VITE_BACKEND_HOST to communicate with the backend, then that looks correct to me as is

By the way, I am actually going to bed now, but I will check back here when I wake up so just throw your questions in here and I'd be happy to answer them when I wake up (assuming someone else doesn't answer them before I wake up)

thank you, this is how my folder looks

RAILWAY_PUBLIC_DOMAIN says it will generate a egress fee and recommend using RAILWAY_PRIVATE_DOMAIN instead, as a first timer in the deployment sector, I need some guidance in this matter.

Is there like an AI assistance ?

Are you part of the Support team, I do not want to bother you this much if you are not a part of the support team at railway, but i'm truly thankful for your help

That is true but remember that frontend code cannot use the private network so if you're connecting to your backend from your frontend code then you need to use the public domain

There used to be but it was cancelled, it was so good too, it's a shame..

I'm just a moderator for the forms (and discord server), I'm not a Railway employee - and no worries at all, I'm happy I can help

Thanks man

I just want to deploy my app for my portfolio but seems too complicated, I will try AWS or Google, I'm unsubscribing from this service. No support from Railway other than developers inside this community. Even I was told by 'Brody' that it can not help me that it will move my concern to the community for help

I'm sorry to see you go

Although just to be clear, on hobby plan you're not promised direct support from Railway, it's listed so on the plans page where you subscribe (see image below)

Best of luck with your portfolio though! Hope you manage to get it deployed

I'm going to go ahead and mark this as solved, feel free to re-open or open another thread if you experience more trouble with deploying on Railway