+1 on not being for production. There are number things besides what has been pointed out that we¹ve learned from running dispatch on Docker such as parameterization, config injection, security (both image & SSL) that need to be addressed. Though I am really, really happy the community is doing so I don¹t have to going forward. That being said, I hope y¹all didn¹t start from scratch on these ;)
Jack Gibson Chief Architect Core Payments Platforms - PayPal On 12/14/15, 5:36 PM, "scholzj" <g...@git.apache.org> wrote: >Github user scholzj commented on the pull request: > > https://github.com/apache/qpid-dispatch/pull/40#issuecomment-164594810 > > I think the idea is good for Dispatch development and testing. But >the images are IMHO not really sufficient for some "more serious" use >(because they are always based on the Git master, because they contain >all the compilers which are not necessary to run the image etc.). Maybe >the README.md should be more clear about that, so that nobody takes image >built using these docker files and uses it in production? > > >--- >If your project is set up for it, you can reply to this email and have >your >reply appear on GitHub as well. If your project does not have this feature >enabled and wishes so, or if the feature is enabled but not working, >please >contact infrastructure at infrastruct...@apache.org or file a JIRA ticket >with INFRA. >--- > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org >For additional commands, e-mail: dev-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
