I'm just catching up with some recent changes to Meltano and I see that MELTANO_UI_PORT is now aliased to PORT, which is convenient as this is what services like Heroku use. Has anyone deployed Meltano to Heroku? If so, how are you setting the PORT env var - in the Dockerfile or a .env file (or some other way)?

@al_whatmough I think @julian_knight is deploying to a Heroku-like system, which is exactly why I added the

PORT

env var! Heroku sets that env var automatically and expects apps to use it, so I don't think you'd need to set it in the

Dockerfile

or

.env

on top of that?

Thanks @douwe_maan and @julian_knight, got some good advice from both of you here and it's helped me get closer to finally having this up and running

You can spin up the Airflow webserver using

meltano invoke airflow webserver

. I assume you are actually running

meltano invoke airflow scheduler

as well?

Yep I have the following script which I invoke at the end of the Dockerfile:

#!/bin/bash
set -e
export MELTANO_DATABASE_URI=$DATABASE_URL
meltano ui start
meltano invoke airflow scheduler

@al_whatmough I think I see the problem! 🎉

meltano ui start

is not backgrounded, so it will never exit, and the script will never get to

meltano invoke airflow scheduler

!

@douwe_maan ah very good point! Well spotted, I'll give that a try

@al_whatmough If you add

&

, it will probably still send its stdout/stderr to your current shell, but it will actually get to the next command