potiuk commented on issue #30499: URL: https://github.com/apache/airflow/issues/30499#issuecomment-1513896449
Correct. This is how airflow works, and we are not going to change it. Airflow webserver shoudl be using gunicorn, subprocess and forking and converting that into single packaged executable is not even remotely at the radar of any of the maintainers or generally speaking has never been discussed in the community. If you wish to pursue your ideas related with packaging airflow. your best bet is raising a discussion at the devlist https://airflow.apache.org/community/ and explaining your motivation, and convincing the broader community that this is needed. Eventually that kind of expectation shoudl find it's way into https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals that you (or someone who picks it up) would descrbe, justify, work out all the details, go through voting process with successful vote and eventually implement most likely. This is how architectural changes in Airflow are supposed to be performed. Converting it into discussion if more explanation is needed. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
