Daniel Iñigo

@vitoravancini, We were using our own coupled _config-to-DAG_ library. For standardization purposes we decided to go with a FOSS solution such as `dag-factory` one (thanks @ajbosco !). I suspect it...

@benbendemo, at least for me the create_user didn't know about the postres connection db, user and password. I'm using this code in a re-packed image ```python import airflow from airflow...

I have to say that, ever since I updated the image to the official iv'e been using some sort of what @harry-cai says. You have a ready installation of airflow...

well @aki1977 how did you enable it?

This repo is not maintained animore. My personal recommendation is using either a managed solution in prod (Astronomer, GCP composer...) And use 'astro' CLI to manage local environments

Also decreasing the number of gunicorn workers from the default 4 to 1 (for local development) worked for me. In the `airflow.cfg` set the following ```toml [webserver] workers = 1...

would this allow for a secret to be set like so? ```yaml services: airflow: image: puckel/airflow secrets: - fernet-key environment: - AIRFLOW__CORE__FERNET_KEY=$(cat /run/secrets/fernet-key) ```

I'm rebasing your changes with my fork, thanks :)

@aalemanq from the [documentation](https://airflow.apache.org/docs/stable/howto/set-config.html#setting-configuration-options) of airflow v1.10.10 > The _cmd config options can also be set using a corresponding environment variable the same way the usual config options can. For...

If you want to get visibility I suggest you file an issue at apache/airflow repo or at StackOverflow (or why not, use both)