Skip to main content
OsmanWa
Level 2
Jan 29, 2025 7:53 PM UTC
Solved

Best Practices for setting up environments for production level EDS website

Hey everyone,

 

We have an EDS website which we want to deploy on our AEM Cloud CDN using Edge Delivery Solution. (Screenshot below)
I do understand the steps needed to configure and connect an EDS website to a Domain. However, this single domain instance will then be our production. I want a staging environment before in this pipeline, so it should somehow look like this:

main----.aem.live ---> www.stagingURL.com ----> www.productionURL.com 

Is that pipeline possible in this configuration for EDS? What are the recommended best practices? 

 


Thank you 🙂 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Tad_Reeves
Tad_ReevesAccepted solution
Adobe Champion and User Group Leader
Feb 3, 2025 1:09 PM UTC

Great question.  I'm assuming that you already have a CDN configuration underway to be able to map your domain to your main--[yoursite].aem.live domain.  If not, I put a bunch of sample CDN configurations for such in a blog post.

But if you want a staging URL, like www-stage.mysite.com, there are two different ways you can map this.  If you're interested in having a CDN in front of the staging CONTENT, you can use the CDN configuration to map to your .page URL to a separate domain using originSelectors in your CDN YAML.  You also may want to make a staging URL that instead uses a specific branch in your code to test that staging branch through the CDN, i.e. something like this: 

originSelectors:
    rules:
      - name: staging
        when: { reqProperty: domain, like: www-staging.mysite.com } 
        action:
          type: selectOrigin
          originName: mysite-staging-url
    origins:
      - name: mysite-staging-url
        domain: stagingbranch--projectname--siteowner.aem.live
        forwardHost: false 

Hope that helps!

View in thread

2 replies

kautuk_sahni
kautuk_sahni
Level 9
Feb 3, 2025 12:32 PM UTC

@h_kataria@shashi_mulugu@kapil_rajoria@tad_reeves@uppari_ramesh@riteshy18@joerghoh@anil_chennapragada@arunpatidar@cr17506599

Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!

Translate
Kautuk Sahni
Tad_Reeves
Adobe Champion and User Group Leader
Tad_ReevesAdobe Champion and User Group LeaderAccepted solution
Adobe Champion and User Group Leader
Feb 3, 2025 1:09 PM UTC

Great question.  I'm assuming that you already have a CDN configuration underway to be able to map your domain to your main--[yoursite].aem.live domain.  If not, I put a bunch of sample CDN configurations for such in a blog post.

But if you want a staging URL, like www-stage.mysite.com, there are two different ways you can map this.  If you're interested in having a CDN in front of the staging CONTENT, you can use the CDN configuration to map to your .page URL to a separate domain using originSelectors in your CDN YAML.  You also may want to make a staging URL that instead uses a specific branch in your code to test that staging branch through the CDN, i.e. something like this: 

originSelectors:
    rules:
      - name: staging
        when: { reqProperty: domain, like: www-staging.mysite.com } 
        action:
          type: selectOrigin
          originName: mysite-staging-url
    origins:
      - name: mysite-staging-url
        domain: stagingbranch--projectname--siteowner.aem.live
        forwardHost: false 

Hope that helps!

Translate
    Terms & ConditionsAccessibility statement

    Loading footer...