It could be a ui.apps package followed by a ui.configpackage. Why should you care? Well, we usually don’t install only 1 CRX package to AEM, but a whole series. I’m not going to describe that part in detail, but I want to zoom in on the parts which are important and rare to find. Our whole process is wrapped inside a Puppet run, which uses Bryan Stopp’s amazing AEM Puppet module (which we forked and modified a little for our purposes) to install the needed packages. You can use the AEM Package Manager user interface, you can drop the file in the crx-quickstart/install folder of your AEM server instances, or you can use the AEM Package Manager REST API. On AEM you make changes by deploying CRX packages. In this Medium post we want to show you the way we have developed to do this safely on AEM package installs, after 5 years of perfecting the process.
We also deploy very often, 10 to 15 times a day and about 2 or 3 times a day to production.Ī way to ensure this process goes smoothly, is to follow the Continuous Delivery principles.īy doing it this way, we constantly improve small things, avoiding big bang releases. What you want when you make changes to your website is that every part of this process goes smoothly.Īt the moment, we have 4 websites running on the Adobe Experience Manager (AEM) content management system and that number will increase. Websites do not magically update themselves, fix their own problems or implement new features.
0 kommentar(er)
