Redis port does not need to be published

Description

Is there a reason to publish redis service port ? It seems to me that publishing it in docker-stack.yml is unecessary (redis is accessed internally in the swarm by other services). When deploying the stack, one can see the published port and try to access it from a web browser but will have the following message which can be confusing :

-ERR wrong number of arguments for 'get' command

Steps to reproduce the issue, if relevant:

1. deploy the stack
2. open http://<host_ip>:<redis_published_port>

[lucj]

You’r right, redis does not need to be published as it’s only used internally by the vote and worker services.

Quick note regarding your example:

Be careful, redis does not expose a http endpoint but a tcp one, if you use a redis client you will be able to connect to the redis service from the outside. Below and nxample when running the stack on play-with-docker.com:

$ redis-cli -h ip172-18-0-10-bahv0ckprd2000cias1g-30000.direct.labs.play-with-docker.com -p 30000
ip172-18-0-10-bahv0ckprd2000cias1g-30000.direct.labs.play-with-docker.com:30000>

Note: as no host port is provided in the redis service, the first one of the range (30000) is mapped to 6379.

[ManoMarks]

Can someone provide a PR for me? There are several compose/stack files, and a kube deployment file.