potiuk commented on issue #60971:
URL: https://github.com/apache/airflow/issues/60971#issuecomment-3790482391
Also - Aritra volunteered on the devlist so I assigned him, But It could
also bee cooperation between several people.
Also @ferruzzi mentors some people with MLH (Major League Hacking) who could
do it or help with it.
It's not super complex to do, I think most of the work will be to work-out
the abstraction in `airflow standalone` to be able to easily switch between
"regular" and "mprocs" proces management - in case of `mprocs` - it handles a
lot of things already - things like signal propagation, quitting, restarting
etc.
But we already have a number of features that should be thoroughly tested
and reviewed and maybe combined with the dev mode as well - to make `airflow
standalone` more usable for "locally developing Airflow" case:
* hot reload - it should nicely work with `airflow standalone` in this case,
but maybe we want to do some better integration (mprocs already supports server
that accept commands and it could easily be used instead of built-in hot-reload
- because the built-in one has some limitations (module reloading might be
problematic)
* (re)building assets automatically when we start stand-alone from sources
And probably some more interesting things that can be found while
implementing and playing with such `--interactive` mode.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
