mik-laj edited a comment on issue #14231:
URL: https://github.com/apache/airflow/issues/14231#issuecomment-779646714


   > So should not we restructure the installation page to do this step-by-step 
installation ? 
   
   This does not always work because we support many installation scenarios and 
configurations and we will not always be able to prepare a guide. I just want 
one page that will allow you to install Airflow from stratch without having to 
make difficult decisions that require expert knowledge and which will help you 
install Airflow in 5 minutes. Also, such an article should not contain 
unnecessary information that is not applicable in a given situation, eg 
information about all kinds of constraints files and extra packages.
   
   Most users aren't interested in whether they use MySQL or PostgresSQL, or 
whether they have LocalExecutor or SequentialExecutor. They only read the 
documentation about it when they have problems. We, as experts, can decide 
which database/executor is best for the novice user. A novice doesn't need to 
know it, because it doesn't make any difference to him, if he just wants to 
quickly start Airflow and try to use it.  If he starts using Airflow, he can 
modify the environment and try to adapt it better to his needs.
   
   > I think the installation page should be the starting point and it should 
explain various installation options - from the simple to advanced ones. Maybe 
there should be separated out to "sub-pages" - each of the option as separate 
page- but they should be simply part of the "installation" area of the docs.
   
   Yes. We can move all the quick start guide to the "Installation" section but 
that is a different issue. To the new "Installation" section, I think it is 
worth moving other articles as well e.g. [Set up a Database 
Backend](http://airflow.apache.org/docs/apache-airflow/stable/howto/set-up-database.html).


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to