GitHub user potiuk added a comment to the discussion: How to deploy to docker swarm with new compose file in the docs?
> The docker-compose of ours is merely an example, not an "official" release of > any sort. So while you can get help from other users, maintainers focus is > not on that, you are mostly on your own and other user's help (but I > recommend just study and learn the version of docker-compose and swarm you > are using, release notes docker-compose and docker-swarm releases and > figuring out the needed changes based on those studies). To be perfectly > honest - you will definitely need to understand a lot there if you sign up to > use both swarm and compose. I am just one of the maintainers. I do not make decisions like that. If you want to propose that Airflow community creates and maintain docker-swarm, you should make such a proposal to devlist (and ideally even contribute it). This is an open-source project maintained by the community - where all "product" decisions, what is supported by the community and to what extent, is discussed on devlist (see "community" tab on our official page - to see discussion archives, how to subscribe. Everything in airflow is decided there and for things like that vote / lazy consensus - and community has to decide to take a burden of maintaining and releasing stuff. But taking into account that we don't even offficially release docker-compose, we merely provide a docker-compose example that everyone should treat as starting point, I doubt we will agree to have a released and supported docker-swarm setup. But you can always try to convince the community at the devlist. GitHub link: https://github.com/apache/airflow/discussions/33115#discussioncomment-14548897 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
