Serving content from localhost for EDS | Community
Skip to main content
New Member
November 12, 2025
Solved

Serving content from localhost for EDS

  • November 12, 2025
  • 2 replies
  • 145 views

We are in the process of migrating our large and complex site from AEM as cloud service to EDS. One thing we wanted to check is if we can serve our content from localhost instead of relying on a cloud instance since we have multiple developers doing lot of POC's and research stories. Is it possible to mount localhost in fstab.yaml or any other means of having local content for EDS?  

Best answer by ruchith53

In EDS, fstab.yaml allows you to mount content paths from AEM Cloud for delivery, but you cannot mount local directories.

When working with the Universal Editor, once the block structure JSON is pushed to your repo, you can create test pages, author blocks in Universal Editor and publish them. After publishing, the content is available locally, letting you customize JS and CSS freely without changing the underlying structure, ideal for frontend experiments and POCs.

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/edge-delivery-services/developing/universal-editor/3-local-development-environment

2 replies

ruchith53Accepted solution
Level 1
January 30, 2026

In EDS, fstab.yaml allows you to mount content paths from AEM Cloud for delivery, but you cannot mount local directories.

When working with the Universal Editor, once the block structure JSON is pushed to your repo, you can create test pages, author blocks in Universal Editor and publish them. After publishing, the content is available locally, letting you customize JS and CSS freely without changing the underlying structure, ideal for frontend experiments and POCs.

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/edge-delivery-services/developing/universal-editor/3-local-development-environment

Greg_Harvell
Level 1
February 17, 2026

We do this, we have test pages in the root ./tests directory, they’re just regular HTML, in the head we import whatever we need from EDS, usually styles.css, scripts/aem.js, scripts/scripts.js, etc. Then in our body we’ll have body > main, and inside that blocks we’re testing with with the raw markup like it would come over from a block usually just the block class on the first div, then the markup. https://www.aem.live/docs/exploring-blocks has a good example of what the accordion block looks like without being rendered yet by decorate for example.