Add a Docker Swarm stack example. #284

[ghost]

No description provided.

[kaiyou]

This looks pretty good, just have a look at the documentation for Docker-Compose about adding proper links to configuration files and I think we can merge.

[kaiyou]

Also, does Swarm support variables in Compose files? in that case, it would be interesting to keep version variables, root path and so on.

[ghost]

I am not sure about vars in the stack file. But I know what there is no .env support (at least yet) - moby/moby#29133 (comment)

[ghost]

And this ^ is why I needed env vars documentation - to at least somehow decrease variable duplication degree in the stack file.

[kaiyou]

Okay then. So I would suggest a couple improvements:

• use the same defaults as for the Compose configuration
• use dynamic links in the document and so on
• add a warning in the documentation that this is for version 1.4 until you support 1.5.

[kaiyou]

Also, could you merge against master?

[rgarrigue]

Hi

I guess setting webdav's image to mailu/none ought to be mailu/radicale ?

Best regards,

[rgarrigue]

And that won't work as is I think

Ignoring deprecated options:

expose: Exposing ports is unnecessary - services on the same network can access each other's containers on any port.

[muhlemmer]

This PR is pretty old, incomplete and the submitter seems to have deleted his Github account (Ghost). Furthermore, the docs seem already to be handled in PR #551.

@kaiyou , I would propose to Close this PR as rejected.

[kaiyou]

Agrees since #551 does a pretty good job of this.