Solved
How to separate content environments (dev/stage/prod) in Edge Delivery Services using fstab.yaml
Hi,
Our team is currently working with Edge Delivery Services and the Universal Editor, using 'aem-boilerplate-xwalk' project.
We understand that we can manage code environments (e.g., dev, stage, prod) by using GitHub branches. And developers and authors can use '?ref=<branch>' to switch between environments they need in UE.
However, when it comes to content, we only have two states available:
'preview' (page)
'publish' (live)
Both of these rely on the same author instance (e.g., 'author-xxx-xxx.adobeaemcloud.com'), which means the content is shared across all environments. Our client requires a separation of content environments for development, staging, and production.
Our initial idea was to configure 'fstab.yaml' to point to different author instances depending on the GitHub branch/environment:
For 'stage', we use: https://<stage-env>.adobeaemcloud.com/bin/franklin.delivery/<owner>/<site>/main
For 'dev', we use: https://<dev-env>.adobeaemcloud.com/bin/franklin.delivery/<owner>/<site>/main
We expected the following URLs to render different content:
'https://stage--<site>--<owner>.aem.page' → showing stage content
'https://dev--<site>--<owner>.aem.page' → showing dev content
But what actually happens is:
The stage URL still displays dev content, despite pointing to different author env in fstab.yaml.
Any suggestions, best practices, or recommendations would be greatly appreciated.