“Regarding documentation, please can you be more specific”
Documentation has multiple references to tutum. At times refing to a Tutum naming convention, at others a Docker Cloud convention.
Cannot fine where it describes the corect naming convention for a default
docker-cloud stack file e.g. tutum.yml or docker-cloud.yml?
No documentation on YML file inhereitence
docker-cloud -f file-one.yml -f file-two.yml
Sparse documentation sarrounding advanced features of the native HAProxy container. One of the main advantages of Docker Cloud.
Documentation describes slack integration, often does not post notifications.
No roadmap on features OR issues.
Much more we don’t have time to do the work for you…
“… What do you think is missing?”
When errors occur in Docker Cloud dialogs appear asking the user to submit a ticket. Nowhere on the cloud.docker.com site is there a “support” url. We had to google this. If there is a link to support from cloud.docker.com please, take a screenshot and post it so we can all learn of its whereabouts. I’am a paying user.
“We have not had any severe service disruptions since release”
Well i cant argue with that when your status page lists 0 downtime and clearly we have had many times we cannot access Docker Hub or the Docker Cloud API is down. I’m sure this forum AND the current issue at hand will attest to that. So why does the status page not reflect this and other downtime detailed within the forums?
“Docker Cloud Build is still in beta.”
Where is this stated? If so why are you charging? People will assume production if “Currently in Beta” is not displayed very clearly within documentation and on the web console itself.