zlatan
10/13/2020, 8:00 PMdouwe_maan
10/13/2020, 8:55 PMinvoke airflow scheduler . If you don't have Kubernetes experience yet and just have a Linux box you can SSH into, it'll be easier to skip containerization and clone the Git repo into a directory, and set up your system's service manager to make sure that meltano invoke airflow scheduler will always be running. The CI/CD job for your repo could then SSH into the VPS and run a little deploy script (that can live in your repo) that will run git pull, pip install meltano, and meltano install (as suggested in https://meltano.com/docs/production.html if you skip the "Containerized Meltano project" sections), followed by the system-appropriate command to restart the meltano invoke airflow scheduler service so that the latest changes are picked up.douwe_maan
10/13/2020, 8:55 PMmeltano install : https://meltano.com/docs/production.html#installing-pluginsdouwe_maan
10/13/2020, 8:57 PMdouwe_maan
10/13/2020, 8:59 PMdocker-compose up -d as a service on your VPS, but then you'd still need to clone the repo on the VPS (since the repo contains the docker-compose.yml file), and you'd still need your CI/CD job to tell the VPS to pull the repo and Docker image again and restart the service, so if you go that route, you won't be getting much benefit from Docker.zlatan
10/13/2020, 9:14 PM