<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Etienne,</div>
<br class="">
<blockquote type="cite" class="">What does thing bring compared to managing IdPs with configuration<br class="">
</blockquote>
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">management
software? I mean you'd need CM anyway to create the IdP's</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">configuration
(whether in the image or external), so why bother with</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Docker
on top of this?</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
<br class="">
</div>
<div>My totally uninformed opinion is that I would use one or the other. You could use both, certainly, but we’re looking at just getting a directory full of files here at the end. Version control remains important, so I would store that in one or more git
repositories, but I don’t know that any more elegant wiring is needed.</div>
<div><br class="">
</div>
<div>Similarly, if I already were doing all of this in a CMS with VM’s with a “cattle" deployment paradigm, I wouldn’t bother with Docker either. There are some real advantages and real disadvantages, but nothing that would make me move yet.</div>
<div><br class="">
</div>
<div>I’m going to be reading about orchestration of containers. That’s one of my favorite CMS features and I don’t know how/whether Docker approaches it, whether through Swarm or other implementations.</div>
<div><br class="">
</div>
<div>Ready for better answers and to look foolish,</div>
<div>Nate.</div>
</body>
</html>