#Setting Another Env Var to Railway Port Value

7 messages · Page 1 of 1 (latest)

tawdry nebula
#

project id: 2090e121-cc62-4fbe-9114-5349121f7893

I'm trying to deploy Metabase via their official docker image. It listens on whatever port is specified by MB_JETTY_PORT and I verified it works by setting my own. I want to pass it the railway port, but when I set MB_JETTY_PORT=${{PORT}} it doesn't pick up any value which I validated with the railway cli.

How should I be passing the Railway port so it gets picked up by Metabase?

novel briarBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

sly forgeBOT
#

Project ID: 2090e121-cc62-4fbe-9114-5349121f7893

safe hull
#

I admire your efforts to get your app to listen on the railway provided port, but that port is only available to your deployment at run time, so sometimes it's just not feasible to do that, just do
MB_JETTY_PORT = 3000
PORT = 3000

#

this tells metabase to listen on 3000, and then it tells railway that your app listens on 3000 as well

tawdry nebula
#

Ahh that makes sense. Thank you!

novel briarBOT