Great webinar today… there seemed to be particular interest in talking about a OOD in a container, and so I thought I’d start a thread about that.
My 2 cents… while having OOD in a container would ease install in some ways, there’s always the issue of customization of containers. And… one strength of OOD is its ability to be customized for each install location – from things as simple as colors / logo to more complex customization like installed apps, job templates, etc. If OOD was containerized, these customizations would not only need to be externalized, but the customization options would have to be well documented, which I find is often failing in downloaded containers.
One option I’ve seen for this that worked well was that the container expected a specific external mapping for customization data and then had a GUI for customization that saved all customization settings to that external mapping. This worked well, but from a container design perspective, it usually means that you have to map many customization save points(/logs, /etc, application save points, …) to that external mapping.
Again, great webinar today,