Add support for Docker Swarm

[gitmapd]

I've organized on my own repository the required files to configure a docker swarm stack.
https://github.com/gitmapd/Canasta-DockerSwarm

I have also a few questions related to it:

• It needs to be added to Canasta-CLI for setting up the stack like it's docker-compose counterpart, so how?
• This setup takes into account the person setting up has a domain and has access to it's DNS because it uses the API of the registrar for it's configuration. So again i ask what's your opinion at it.

Let me know thank you.

[jeffw16]

I've organized on my own repository the required files to configure a docker swarm stack.
https://github.com/gitmapd/Canasta-DockerSwarm

As we saw in one of our prior Canasta meetings, this seems pretty cool. However, it is customized quite extensively and does not reflect the same approach taken by the Canasta for Docker Compose stack. So, in order to add support for Docker Swarm, I think we should at least start by trying to reach feature parity: adding missing features and removing extraneous curation.

Furthermore, since Swarm is more similar to Kubernetes than it is to Docker Compose, it might be worth coming up with a new spec that should be applied for both K8s and Swarm, and that spec should probably be different from the one for Docker Compose, but only when there is a technical necessity for the difference. For instance, networking is more complex in Swarm and K8s compared to Compose, so that will need to be appropriately accounted for. However, there would not be any reason to add more complexity to the already very easy process of setting up Canasta using Docker Compose.

It needs to be added to Canasta-CLI for setting up the stack like it's docker-compose counterpart, so how?

We already offer a flag, -o, in the Canasta CLI to choose which orchestrator should be used.

[gitmapd]

I meant to say that my configuration is as you said towards a more niche since it automates the domain renewing so nice more configuration. A segunda, 20 de fev de 2023, 19:58, Jeffrey Wang ***@***.***> escreveu:

…

I've organized on my own repository the required files to configure a docker swarm stack. https://github.com/gitmapd/Canasta-DockerSwarm <https://github.com/CanastaWiki/Canasta-DockerCompose/issues/url> As we saw in one of our prior Canasta meetings, this seems pretty cool. However, it is customized quite extensively and does not reflect the same approach taken by the Canasta for Docker Compose stack. So, in order to add support for Docker Swarm, I think we should at least start by trying to reach feature parity: adding missing features and removing extraneous curation. Furthermore, since Swarm is more similar to Kubernetes than it is to Docker Compose, it might be worth coming up with a new spec that should be applied for both K8s and Swarm, and that spec should probably be different from the one for Docker Compose, but only when there is a technical necessity for the difference. For instance, networking is more complex in Swarm and K8s compared to Compose, so that will need to be appropriately accounted for. However, there would not be any reason to add more complexity to the already very easy process of setting up Canasta using Docker Compose. It needs to be added to Canasta-CLI for setting up the stack like it's docker-compose counterpart, so how? We already offer a flag, -o, in the Canasta CLI to choose which orchestrator should be used. — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL55ONX3SXNL6QGKZD6MABDWYPEGBANCNFSM6AAAAAAUASY6TA> . You are receiving this because you authored the thread.Message ID: ***@***.***>