cfg: changed airflow config to allow using the celery executor

airflow.cfg

@@ -27,7 +27,7 @@ default_timezone = utc
 # ``SequentialExecutor``, ``LocalExecutor``, ``CeleryExecutor``, ``DaskExecutor``,
 # ``KubernetesExecutor``, ``CeleryKubernetesExecutor`` or the
 # full import path to the class when using a custom executor.
-executor = SequentialExecutor
+executor = CeleryExecutor
 
 # This defines the maximum number of task instances that can run concurrently per scheduler in
 # Airflow, regardless of the worker count. Generally this value, multiplied by the number of
@@ -45,7 +45,7 @@ parallelism = 32
 max_active_tasks_per_dag = 16
 
 # Are DAGs paused by default at creation
-dags_are_paused_at_creation = True
+dags_are_paused_at_creation = False
 
 # The maximum number of active DAG runs per DAG. The scheduler will not create more DAG runs
 # if it reaches the limit. This is configurable at the DAG level with ``max_active_runs``,
@@ -708,7 +708,7 @@ access_logformat =
 expose_config = False
 
 # Expose hostname in the web server
-expose_hostname = False
+expose_hostname = True
 
 # Expose stacktrace in the web server
 expose_stacktrace = False
@@ -954,7 +954,7 @@ worker_enable_remote_control = true
 
 # The Celery broker URL. Celery supports RabbitMQ, Redis and experimentally
 # a sqlalchemy database. Refer to the Celery documentation for more information.
-broker_url = redis://redis:6379/0
+broker_url = redis://localhost:6379/0
 
 # The Celery result_backend. When a job finishes, it needs to update the
 # metadata of the job. Therefore it will post a message on a message bus,

docker-compose.yaml

@@ -140,6 +140,8 @@ services:
     image: redis:latest
     expose:
       - 6379
+    ports:
+      - 6379:6379
     healthcheck:
       test: ["CMD", "redis-cli", "ping"]
       interval: 10s