rossturk opened a new pull request, #25888: URL: https://github.com/apache/airflow/pull/25888
I have been studying Airflow's web analytics, and noticed that the Docker Compose Quick Start is a page that stands out a bit - people spend a lot of time here compared to other pages. So I started to investigate. The language on that page is currently very strong, discouraging its use for almost all situations. I had a few conversations with @potiuk and others about this page and heard a repeated opinion that `airflow standalone` is a better procedure for those just getting started. The standalone Quick Start procedure has no such disclaimers, and is far simpler. After using that method for a few projects, I think I agree. However, I don't think that a strongly worded warning on the Docker Compose procedure is the best way to communicate that the standalone procedure is better. Instead, I think the Docker Compose procedure should be made into a How To, and the standalone procedure should take its place. This will clearly communicate the preference for the standalone procedure without making the Docker Compose unavailable to those who rely upon it. This PR is intended to: 1. Restore `start/local.rst` to `start.rst` 2. Move `start/docker.rst` and associated assets to `howto/docker-compose/` 3. Update links throughout to point at these new locations 4. Create redirects to support these moved resources 5. Reduce warnings in the Docker doc, now that it's not so prominent 6. Misc copy updates in Docker doc, since I was in there :) Signed-off-by: Ross Turk <[email protected]> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
