Since AEM as CS package manage doesn't allow to deploy the code changes due to immutability of the system, but AEM as CS package manager allow to upload and install the content packages that includes paths like /content, /etc.
Here, instead of using package manager for deployment RDE is using AppBuilder and pushing the locally build zip, jar files in AEM as CS RDE instance. Below are the detail about the Rapid Development Environment in AEM as CS development environment setup and uses of it.
How to setup Rapid Development Environment in AEM as CS?
1. First we need to enable the RDE instance for that you have to contact Adobe CSE/Support to get that enable under your license.
2. We need to install node and adobe cli to make the development setup and running in local machine.
To enable and setup follow the steps given here: How to set up Rapid Development Environment | Adobe Experience Manager
How to use Rapid Development Environment in AEM as CS?
Using Rapid Development Environment is easy using adobe cli, for every task we have to just run one liner command on cli. To learn more and see the steps and action that is possible with RDE please follow the steps given in this document; How to use Rapid Development Environment | Adobe Experience Manager
Rapid Development Environment is going to make the developer life easy and this could be use by a developer at a time. Multiple developers could also use but that required very frequent sync between developers code. The biggest advantage of rapid development environment is that; we now use a full AEM as cloud service instance as a local. Where one can make the changes and deploy the code on cloud service without commit, and running the cloud manager CICD pipeline which taking approximately 40 minutes to make our code live on any AEM CS instance.
No comments:
Post a Comment