Challenge deploying different services from a mono repo
rootmateo
PROOP

2 years ago

This is my first time trying to run multiple services from 1 repo on railway. (It's pretty straight forward when there's 1 docker file per repo).

My repo has a services/ directory with multiple services. Each has a dockerfile.

I'm not sure how to best go about deploying this on railway.

Closed

20 Replies

rootmateo
PROOP

2 years ago

92c5e847-f796-4ffc-b29f-0c2a9bc86322


2 years ago

is there anything not answered by these two doc's pages?


rootmateo
PROOP

2 years ago

So these were fantastic resources. I followed them and have my 'service' created but I don't know how to point it to the Dockerfile


2 years ago

have you set the root directory?


rootmateo
PROOP

2 years ago

Yes I set it as the root of the project (default) because that is where the lib/ folder is which is used in building the docker container.


rootmateo
PROOP

2 years ago

as shown here I believe


rootmateo
PROOP

2 years ago

Each service uses the lib/ and jasper/ directory.


2 years ago

ah then that's a shared monorepo


rootmateo
PROOP

2 years ago

Yessir!


rootmateo
PROOP

2 years ago

Again thank you so much for your help man. I don't understand how you guys become so knowledeable in this space 😄


2 years ago

please see this docs section then -


2 years ago

for me, I've gained this knowledge just by helping


rootmateo
PROOP

2 years ago

Incredible. Let me quickly give that a shot, looks exactly what I need


rootmateo
PROOP

2 years ago

Everything's up and running. Thx boss!


rootmateo
PROOP

2 years ago

Hey @Brody Might I ask 1 more quick question?


rootmateo
PROOP

2 years ago

How comfortable should I feel, or rather, would you recommend sensitive keys (like API keys, etc) be passed into the docker container via the variables section?


rootmateo
PROOP

2 years ago

I notice that there is a way to SEAL these variables however I noticed that there was a bug when done this way, where the variables (only the SEALED ones) aren't available to the container.


2 years ago

there shouldn't be that kind of bug, but if you are the only one who has access to the project you have zero reason to seal the variables


rootmateo
PROOP

2 years ago

Gotcha thank you! How can I close out this ticket 🙂 Your help's been greatly appreciated!


2 years ago

we dont close, we just do that! 🙂


Welcome!

Sign in to your Railway account to join the conversation.

Loading...