AEM RDE Reset Recommendations

[kashifs21709560]

Are there any recommendations for resetting RDE?

Do we need to reset it regularly with every Cloud Service release or can it go on without reset for a few months?

[Nishant-Singh]

Resetting the Remote Development Environment (RDE) is a common practice to ensure a clean and up-to-date development environment. RDE is a cloud-based environment that allows developers to work on AEM projects without the need for local installations. Resetting RDE means restoring the environment to its initial state, usually after applying updates or changes, to ensure a consistent and stable development environment.

The frequency of resetting RDE may vary based on your development needs and the release cycle of the Cloud Service. Here are some general recommendations regarding resetting RDE:

1. After Major Updates: It is advisable to reset RDE after major updates or Cloud Service releases. This ensures that you are working with the latest version of AEM and that any new features, enhancements, or bug fixes are applied to your development environment.

2. Before Starting New Projects: If you are starting a new AEM project or a significant feature development, consider resetting RDE. This provides a clean slate to begin your development and ensures that the environment is consistent and free from any previous configurations.

3. After Prolonged Usage: If you have been using RDE for an extended period, there might be accumulated configurations and changes that could impact the stability and performance. Resetting RDE periodically helps maintain a clean and well-optimized development environment.

4. Before Debugging Environment Issues: If you encounter issues with your RDE, resetting it can be a troubleshooting step to rule out any potential configuration-related problems.

5. As Needed: While resetting RDE regularly after Cloud Service releases is generally recommended, the exact frequency depends on your development needs and the stability of your projects. If your development environment is working smoothly and you have not faced any major issues, you can continue using it without resetting for a few months but it should be same or higher version of the production release.

Remember that resetting RDE will remove any custom configurations, content, and data that you may have added, so it's essential to back up any critical data or code changes before proceeding with the reset.

[kashifs21709560]

@Nishant-Singh Appreciate your detailed response. 

Do you have any recommendations for updating content and assets on RDE after the reset?

For Content I know it can be either checked in the repository or content packages can be use but for assets say more than 100 GB what are your recommendations for updating the RDE servers after the reset?

Thank you,

Kashif

[Tanika02 · Accepted solution]

Hello @kashifs21709560 - 

When an RDE is reset, all content is removed and so if desired, explicit action must be taken to add content. As a best practice, consider assembling a set of content to be used as test content for validating or debugging features in the RDE. There are several possible strategies for populating the RDE with that content:

1. Sync the content package explicitly to the RDE using the command line tooling

2. Place and commit the sample content in git inside an install.rde folder under /apps and then sync the overarching content package to the RDE using the command line tooling.

3. Use the content copy tool to copy a defined content set from prod, stage, or dev environments, or from another RDE.

4. Use Package Manager

Note that you are limited to 1GB when syncing content packages.

Additionally, you can also refer some quick links to get more details about AEM RDE Recommendations here : 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo... 

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/developing/rde/overvi... 

https://www.youtube.com/watch?v=SnNNsTJ5tAw