for testing the app internally (specifically the case where we want john to be able to test the ui) seems like there are two options: 1. just write up instructions for how to set it up and run it locally (with docker, etc) 2. host it on our gcp or aws infra so that john can interact with it just via some url has anyone thought about this already? probably just going to do 1 to get john up and running this afternoon 2, but i think 2 might be a good thing for us to set up in the future.

I think I'd go for 1 for now. Easier to have a pull & docker-up workflow

but separately I think 2 is actually a great thing to setup and even potentially make public

guys 🙂

for instant try out

we have it already

it is in our documentation

git clone & docker compose

that's a good exercise for @John (Airbyte) to try to follow these instructions (might need to do the VERSION=dev hack though

I think having #2 would make it so that we have to feel the happiness (or pain) of continuously managing/deploying the app

so that's the thing we might need to document

@John (Airbyte) do you want to try to follow our public instructions and see how it goes?

sure let's do that

I was able to. pretty easy actually. my only comment was that it would be great to have an indicator in the terminal once the app is finished loading (after the 100 lines of "dataline-scheduler")

great!