All good points:
> So in standaonle mode we would need to mound one "dummy process"
panel giving the key "getting started" information with UI URL and
admin user/password at least.
Great idea
> We should not make it harder for users for first-time user
experience. Today after a `pip install apache-airflow` you are
potentially good to go
Yes. Likely we can leave standalone behaviour working as of today by default
> We therefore might consider
not naming it `--mprocs` but rather `--interactive` to describe the
use case?
I really like this flag idea.
> On the neutral side though I am not sure if a first time user is
"easier" with merged logs to see errors of if a first time user might be
overwhelmed with too many panels to scroll in to find an error not
knowing which component maybe raising a stack trace at all.
Yep. With `--interactive` flag as non-default this issue would also be
handled.
