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 2022/06/03 12:45:23 UTC

[GitHub] [airflow] malthe opened a new issue, #24163: Service profiles for Docker Compose

malthe opened a new issue, #24163:
URL: https://github.com/apache/airflow/issues/24163

   ### Description
   
   Docker Compose is arguably the most straight-forward way to stand up an Airflow system on a local machine.
   
   It should be possible to tailor the deployment based on [profiles](https://docs.docker.com/compose/profiles/).
   
   We already have `debug` and `flower`, but it seems ideal to attach a profile to `postgresql` as well. Many users would want to  use `sqlite` for local development and don't need `redis` or `airflow-worker`.
   
   ### Use case/motivation
   
   The main motivation is to reduce the deployment to the bare minimum to get started with local development of DAGs.
   
   Basically, running just the scheduler, triggerer and webserver, against a `sqlite` database.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [airflow] eladkal closed issue #24163: Service profiles for Docker Compose

Posted by "eladkal (via GitHub)" <gi...@apache.org>.
eladkal closed issue #24163: Service profiles for Docker Compose
URL: https://github.com/apache/airflow/issues/24163


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [airflow] potiuk commented on issue #24163: Service profiles for Docker Compose

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #24163:
URL: https://github.com/apache/airflow/issues/24163#issuecomment-1146211966

   I dont think we should provide a configurable Docker Compose beyond quick start. 
   
   Who is going to supprt problems that people are going to have wihen they start modifying Docker Compose and get errors there? You can look up how many of the users already assumeed this is "official" docker compose and raised issues that this and that does not work there. If we make it configurable and "deployable", we automaticaly assume the responsibility on supporting all kinds of configurations there. 
   
   I am strongly against going this route.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [airflow] potiuk commented on issue #24163: Service profiles for Docker Compose

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #24163:
URL: https://github.com/apache/airflow/issues/24163#issuecomment-1146212831

   It's much, much better to make `airflow standalone` "small-production-ready". That would be far easier to complete and super easy for "casual users" to start airflow without learning docker compose and images. 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org