f78d75b5-8972-4d61-8517-22bbccefb41e

Do i need to add each service start command to the root package.json?

@Brody This is what I have:

root package.json

"kangiten:start": "pnpm --filter kangiten start"

yes you do, like a start:backend and start:frontend etc

but

it does fail build though

let me run that script for logs

1271628078660976692

beat you

dang

is pnpm-lock.yaml absent?

does the service need to have that? it's a golang app

it's in the root

does the go app need to access code from any other folder?

yeah, I have a shared package for other golang services

okay, do you have a kangiten:build script?

oh i need to set a specific one too? whoops

i just had the turbo build one lol

go apps need to be built

yeah i just assumed it ran turbo build thats mb

youd want app specfic build scripts

gotcha

this package json gonna be long haha

do you have this set too? -

Yeah

you taught me not too long ago

you may have added the new build script but you didnt configure the railway service to use it

ahh this error
WARN  Local package.json exists, but node_modules missing, did you mean to install?

ive had it before

actually its a go error
```sh: 1: go: not found

/app/services/kangiten:

 ERRPNPMRECURSIVERUNFIRST_FAIL  kangiten@0.0.0 build: go build -o bin/kangiten main.go

spawn ENOENT

 WARN  Local package.json exists, but node_modules missing, did you mean to install?

 ELIFECYCLE  Command failed with exit code 1.

error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

exit status 1```

i set provider to Go though

looks like it didnt take, try removing and readding node and go

same error

this must be the issue - i dont see Go in here

your providers list is only go though

Yeah ive been changing them

you want to set it to node and go

yep it still fails

might be time to move to a nixpacks.toml, i dont think you can pass in providers when you use the v2 builder

ok ill look into that, i ahvent used a nixpacks toml file before

Is this the correct way to do it. I added a railway.toml to the root of my monorepo with the following:

[build]
builder = "NIXPACKS"

providers = ["node", "go"]

tbh i dont know the syntax for the railway.toml file off the top of my head.

so cant hurt to try

should this stay this way?

gotcha

yeah its not being used anyway

yeah it might have to be under a key, but the docs dont specify

under a key?

like [build]

sorry idk what its called in toml

yeah based on on the jsonschema it does, let me revisit

seems that even then it still doesnt work

syntax might be wrong, or you placed the file in the wrong location (need to be on root)

i forgot, the v2 builder does not support nixpack configs in a railway.toml/json

use a nixpacks.toml file

ohhh

same issue with nixpacks.toml

alright, Dockerfile time

or disable the v2 builder

do yall have any docs or examples for monorepos? i dont have a lot experience with dockerfiles in monorepo. disabling v2 didnt work

from what im seeing i guess i could make a dockerfile for each service with custom docker file path https://docs.railway.app/guides/dockerfiles

you switched the runtime back to legacy, that should stay on v2.

you wanted to switch off the new builder

but docs on how to write a Dockerfile would not be specific to railway so it would be out of the scope of our docs

no worries

you mean the new builder env?

yeah

but that looks like its not going to work, so dockerfile for sure

@Brody I see some people having the Cache mount ID is not prefixed with cache key which I am myself having but don't see the issue <:Thonk:264701195573133315>

# Build stage
FROM golang:1.22.5 AS builder

# Set working directory
WORKDIR /app

# Copy go mod and sum files
COPY go.mod go.sum ./

# Set the service name (change this for each service)
ARG SERVICE_NAME=kangiten
ARG SERVICE_ID=fc824b79-e4db-4095-9801-b99985b8f4c8

# Download dependencies
RUN --mount=type=cache,id=s/${SERVICE_ID}-/root/cache/go-build,target=/root/.cache/go-build \
    go mod download

# Copy source code
COPY . .

# Build the application
RUN --mount=type=cache,id=s/${SERVICE_ID}-/root/cache/go-build,target=/root/.cache/go-build \
    CGO_ENABLED=0 GOOS=linux go build -o /app/main ./services/${SERVICE_NAME}

# Final stage
FROM alpine:3.18

# Set working directory
WORKDIR /app

# Copy the binary from the builder stage
COPY --from=builder /app/main .

# Run the binary
CMD ["./main"]

actually just hardcoding the id without $service_id worked

unfortunately you need to hardcode the service id

awesome

holy shit it works

thanks for all your help @Brody 🙏

no problem, dockerfiles imo are better for most things than doing a dance with nixpacks

Can't this be fixed? it is very annoying that we have to create separate dockerfiles for each service; it's a huge time waste especially for those who don't know they have to hardcode it.

I just completely removed cache mounts (at the expense of +2min build times). I honestly think we (users) are not meant to go through such hacky processes. Perhaps many other power users (that like running things efficiently) will share the same

Railpack is a great option for you then!

!s