hey, can you be more specific on what does not deploy? Did you try it?

extra info:
his repo https://github.com/Melvineitor/FinalDestination

he's trying to deploy an api inside /inmo/api

it's all ai generated

@AkuaFR

i have a project using angular as frontend and an asp.net api as a backend
im trying to make a hosting for the app in, and the frontend loads just fine
but the backend has given me a lot of trouble
im trying with a docker file, but it is not working
right know, it shows me this
"dotnet restore" did not complete successfully: exit code: 1
MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

what's this

FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
WORKDIR /src

# Copy csproj and restore dependencies
COPY ["api.csproj", "./"]
RUN dotnet restore

# Copy the rest of the code
COPY . .
RUN dotnet build "api.csproj" -c Release -o /app/build
RUN dotnet publish "api.csproj" -c Release -o /app/publish /p:UseAppHost=false

# Final stage/image
FROM mcr.microsoft.com/dotnet/aspnet:9.0
WORKDIR /app
COPY --from=build /app/publish .
ENTRYPOINT ["dotnet", "api.dll"]

can you try the dockerfile above?

make sure to set the following environment variables on your Railway service:

ASPNETCORE_URLS=http://0.0.0.0:8080
PORT=8080

alright

its not my project and u know

im just helping

its giving the same msg

Nixpacks is not detecting that you're using a Dockerfile, in the Railway dashboard did you set a root directory?

i did

Ok, then tell Railway to use it, add a RAILWAY_DOCKERFILE_PATH=Dockerfile environment variable to your service. If it fails to encounter that path, try to use the full path RAILWAY_DOCKERFILE_PATH=/inmo/api/Dockerfile

it loaded
but it loaded the frontend instead of the backend
even tho it detected the docker file

Oh, then use the full path. Railway does not take into account the root directory that you set earlier.

inside the dockerfile..

What do you mean?

nvm

give me a sec

/inmo = loads the frontend
/inmo/api = error

what error does it give? paste full build logs

are you sure you did change the Dockerfile? seems like it's using the old one

change this one, not the root one

that's it

got it

it loaded the "API is running"

now trying to make the http methods work

so everything's working?

everything is running, yes
not necessarily working
still gotta fix the enrouting

ill let you know

(he deployed it successfully, we talked in dms)

!s

mmm

!s

hmm…

!s

dammit