potiuk edited a comment on issue #14231: URL: https://github.com/apache/airflow/issues/14231#issuecomment-779272344
Thanls @sdanbury for feedback There are two parts of the setup: 1) Local dev env (and it indeed is always "brittle" because of the dependencies and it is generally harder to keep it in sync with the changes and new dependencies added (and especially with the CI environment where we run most of the tests) 2) Breeze - which is local Bash + docker-compose/docker setup. Breeze environment is in fact dockerized environment under the hood and the breeze script mainly automatically manages the docker environment for you and makes it easy to run certain configurations (databases/integration/python versions) as well as run some common tasks in a consistent way (such as building images, building documentation, running consistent static code checks etc). Also it is identical to the environment used in CI - so you can very easily replicate any of the problems you see in the CI with it. It is also meant to be easy for anyone - even by people who have no prior docker experience but still makes use of the docker goodies (i.e. consistent development environment shared between people). Both of them have different purposes (https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#development-environments) Could you please elaborate a bit more what your problems were with the dependencies? * Were the problems you mentioned more on the local dev env setup or the Breeze env setup (the dockerized) one? * What did you mean by 'docker-based" workflow. How would that be different from Breeze? I know a few committers who are more experienced and familiar with docker are running their own docker or docker-compose environments. We also (as of recently) have a simple way to "use" (but not develop) Airflow with docker-compose (https://github.com/apache/airflow/blob/master/docs/apache-airflow/start/docker.rst) I'd love to hear more from the fresh contributor perspective on how we can improve the experience here :) Maybe you already can have some proposals and even PRs on how to improve our documentation/workflow process? It would be awesome to get it from a "newcomer" but with some experience, to see how many assumptions we have in our heads and how the "initial" experience can be improved. ---------------------------------------------------------------- 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]
