potiuk commented on issue #60971:
URL: https://github.com/apache/airflow/issues/60971#issuecomment-3790447898

   Yes. It shoud be "truly standalone".
   
   The idea to make it totally independent from `breeze` - so that it does not 
require docker **at all**. Also this is both for those who want to just start 
airflow, try it and - for example - do some testing with their Dags, as well as 
for those who might want to have a nicer and quicker (but very limited) 
replacement for `start-airflow` - without the overhead of containers.
   
   This means that it should not rely on mprocs being installed - it should 
download and install (well make it runnable internally in some cache in 
AIRFLOW_HOME most likely) mprocs automatically (ideally with some consensus of 
the user that should be asked for it unless they specify something like 
`--answer yes`. This is easy as mprocs publishes multi-platform binaries (it's 
a rust project) that are somewhat big binaries - but not **too** big and 
"standalone" as well - means they do not need any 3rd-party libraries. So it's 
just the matter of pulling and unpacking the binary that is right for the 
architecture we are in (on failing in case our architecture is not supported) .


-- 
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]

Reply via email to