tggm803sc commented on issue #16031:
URL: https://github.com/apache/airflow/issues/16031#issuecomment-6858667116
Hi — I'd like to pick this up.
I checked `main`: the only compose example in
`airflow-core/docs/howto/docker-compose/` is
still the CeleryExecutor one, and there's no PR linked to this issue. If the
person who
commented on 4 Nov is still working on it, let me know and I'll step back.
I'm going the "more examples" route rather than the generator/wizard, per
the earlier
discussion on the issue. Here's the shape I've already prototyped:
- A second file, `docker-compose-localexecutor.yaml`, with LocalExecutor +
PostgreSQL and
nothing else: `postgres`, `airflow-apiserver`, `airflow-scheduler`,
`airflow-dag-processor`, `airflow-triggerer`, `airflow-init`, plus the
optional
`airflow-cli` debug service. No Redis, no `airflow-worker`, no Flower.
- A short page next to the existing guide: when LocalExecutor is the right
choice, init,
run, shut down, and a note that task logs come from the scheduler
container because
there is no worker to read them from.
- Adds the page to the howto toctree, and cross-links it from the
CeleryExecutor guide.
Both files pass `docker compose config` and `yamllint`. I have not run the
stack end to end
yet — that's next, before I open the PR.
Three things I'd rather not guess at:
1. **Placement.** Is
`airflow-core/docs/howto/docker-compose/docker-compose-localexecutor.yaml`
the right home? I want to be sure a second YAML in that directory is
published the same way
`docker-compose.yaml` is, so the new page can offer a `curl` download
from the docs URL. If
that directory is meant to hold only the quick-start file, what would you
prefer — a
subdirectory, or a page somewhere else?
2. **Auth manager.** The existing example sets `AIRFLOW__CORE__AUTH_MANAGER`
to FabAuthManager,
which is what makes `_AIRFLOW_WWW_USER_CREATE` give the
`airflow`/`airflow` login.
SimpleAuthManager is the 3.x default but manages users through
configuration, so that same
init step produces no user at all. Should the new example stay consistent
with the existing
one (FAB), or demonstrate the default and document the generated password
instead?
3. **How many variants.** The issue mentions several configurations
(LocalExecutor, MySQL, …).
Is one LocalExecutor + PostgreSQL example the useful increment, or would
you rather see a
small set in one PR?
If any of this is already settled somewhere, point me at it and I'll follow
that; otherwise
I'll go ahead with the above and open a PR referencing this issue.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
