Deploy monorepo project that has dependencies on other packages with Docker.
ionkorol
PROOP

a month ago

Second question that i am hopping to get an answer on.

I have a mono repo with folders backend and shared. Backend has dependency on shared but how can I copy dependency if I am deploy only backend and railway only packages the backend folder code.

$10 Bounty

9 Replies

ionkorol
PROOP

a month ago

Wondering if I can move the Dockerfile to root but how can I specify which dockerfile to use for the up command if I have multiple Dockerfiles ?

ilyassbreth
FREE

a month ago

the trick is:

  1. don't set any root directory in railway settings , this lets it clone your whole repo including shared folder

  2. add a variable in railway called RAILWAY_DOCKERFILE_PATH and set it to like /backend/Dockerfile (or wherever yours is)

  3. in your dockerfile, since build context is from root, just do:

COPY ./shared ./shared
COPY ./backend ./backend

basically railway always builds from repo root regardless where dockerfile is, you just tell it which dockerfile to use with that env variable. works for multiple services too, each gets its own RAILWAY_DOCKERFILE_PATH

ilyassbreth
FREE

a month ago

i hope this was clear, let me know if you need more clarification

ionkorol
PROOP

a month ago

I want to use railway up cli command. is there an option I can pass to it. like fly cli has --dockerfile and --config options

ionkorol
PROOP

a month ago

But also can't even run a command from root cause project "is not linked" can we not just pass the project id to the command. It all seems so limited

ionkorol
PROOP

a month ago

RAILWAYDOCKERFILEPATH doesn't even work

ilyassbreth
FREE

a month ago

so the issue is the variable name , it's RAILWAY_DOCKERFILE_PATH with underscores, not "RAILWAYDOCKERFILEPATH" all together

here's what actually works:

  1. don't set root directory in your service settings , leave it empty so railway clones your whole repo (both backend and shared folders)

  2. in your service dashboard go to variables tab and add: RAILWAY_DOCKERFILE_PATH = /backend/Dockerfile

  3. for cli usage from root:

  • run railway link from your monorepo root (it'll ask which service to link)

  • then railway up works

  • there's no --dockerfile flag in railway cli like fly has, it uses the service variable instead

  1. in your dockerfile use paths relative to root since build context is always from repo root:

dockerfile

COPY ./shared ./shared
COPY ./backend ./backend
WORKDIR /backend

the key thing is railway cli doesn't have --dockerfile flags. you set RAILWAY_DOCKERFILE_PATH as a service variable in the dashboard (with underscores), and railway up will use it automatically

ilyassbreth

so the issue is the variable name , it's RAILWAY_DOCKERFILE_PATH with underscores, not "RAILWAYDOCKERFILEPATH" all togetherhere's what actually works:don't set root directory in your service settings , leave it empty so railway clones your whole repo (both backend and shared folders)in your service dashboard go to variables tab and add: RAILWAY_DOCKERFILE_PATH = /backend/Dockerfilefor cli usage from root:run railway link from your monorepo root (it'll ask which service to link)then railway up worksthere's no --dockerfile flag in railway cli like fly has, it uses the service variable insteadin your dockerfile use paths relative to root since build context is always from repo root:dockerfileCOPY ./shared ./shared COPY ./backend ./backend WORKDIR /backendthe key thing is railway cli doesn't have --dockerfile flags. you set RAILWAY_DOCKERFILE_PATH as a service variable in the dashboard (with underscores), and railway up will use it automatically

brody
EMPLOYEE

a month ago

That user sent the message on Discord, they had underscores in their original message and they got stripped somehow during the bridge from Discord to CS.

crisog
MODERATOR

a month ago

Next CLI release will support this <:salute:1137099685417451530>

Loading...