Hi Jarek! I like this idea. We use airflow standalone a lot and more often its hard to identify issues when the log is multiplexed onto the screen. Also new users who are unaware that airflow drops a .json with a temp account in airflow home often find themselves scrambling to quickly copy the auto generated credentials before it vanishes into history.
I can see instances where you may want to restart individual services (dag processor, etc) without having to kill the whole standalone run and launch a new one. Having separate logs for each service and a way to manage each one separately would be amazing I also agree with Jens here as to making the first time standalone run working with the most minimum number of commands as possible (pip install apache-airflow && airflow standalone) Adding these via additional options would be nice! Thanks Dheeraj On Tue, Dec 23, 2025 at 2:42 PM Jarek Potiuk <[email protected]> wrote: > 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. >
