Musings on the Human Condition

An instance can contain multiple web sites. Each web site can contain pages for multiple languages and locales (i.e. regions). OSGI configurations are global (i.e. they apply universally across the entire instance) and are used to control things like how many old versions of a page to keep as a page goes through modifications or edits. Most OSGI configurations can be as loose or as tight as you want them to be. If they are loose, they allow more control at the individual web site level. If they are tight, they allow less control at the individual web site level. All remaining elements of an AEM setup, such as user groups and users, assets (images, videos, PDFs), OSGI bundles, code, templates, components, rollout configurations, workflows, integrations, etc. can be seamlessly made available across an instance. Individual web sites can choose to reuse them or create their own. Reuse is easier across a single instance but also achieved easily enough across multiple instances via ...

There's a lot of confusion out there about the terms virtualization, containerization, etc. and the related products such as Vagrant, Docker, VirtualBox, etc. When do I use what? I like to think of it this way. The physical machine could be a Mac or a Windows PC or laptop. VirtualBox is an Oracle product that provides the virtualization layer, thereby allowing you (for example) to run Linux on a Windows machine. You can configure the resources (disk, CPU, RAM) you want to allocate to each virtual machine (VM). Vagrant is for consistent environment management paradigms across all platforms/OSs. You can use it to install base software for you application, e.g. the Apache web server. Docker is for containerization and only runs on Linux because it uses Linux's container facility to do its thing. So, it used to be that if you're using Windows, you had to run VirtualBox or some virtualization software to stand up a Linux machine first before you could install D...