You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/02/15 15:40:00 UTC

[GitHub] [airflow] sdanbury edited a comment on issue #14231: Quick start for Airflow on Mac OS

sdanbury edited a comment on issue #14231:
URL: https://github.com/apache/airflow/issues/14231#issuecomment-779297831


   Apologies, I think there was some initial confusion on my part. It appeared on the surface that breeze was mainly a non-containerised approach, but it appears to be a hybrid approach as you say (some of it uses docker/docker-compose, some doesn't).
   
   The confusion was mainly around the `./breeze initialize-local-virtualenv --python 3.6` step, which I believe falls into your `1. Local dev env` point above. This took a really long time for me on my setup. Most of the issues were raised by @mik-laj in the issue description; some examples:
   - `cryptography` requiring a rust compiler
   - [This issue](https://github.com/pyca/cryptography/issues/3489) requiring me to set some environment variables
   - Needing to `brew install mysql`
   
   There were a few other little things. Without a fully containerised setup (where you don't need a local venv) I can't see a quick way of getting past stuff like this, you just have to invest the time upfront, hopefully get through it and create docs. Although I appreciate that this isn't always possible for newcomers to the project.
   
   I have worked with Airflow for a couple of years now and have always just rolled my own local setup. We are running airflow on k8s with the k8s executor and I wanted to revisit my local airflow setup, hence why I started going through this process.
   
   Very keen to begin contributing back. This seems like a great place to start. I will continue down this path, gather some thoughts together and open some PRs if I come across something.


----------------------------------------------------------------
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:
users@infra.apache.org