I went through the tutorial, https://www.aem.live/developer/tutorial, and the tutorial has us share a folder to helix@adobe.com. Is this the same process on production?
On the development documentation, it also says our github needs to be public and URLs are produced, https://<branch>--<repo>--<owner>.aem.page/ In the example above that’s https://main--mysite--aemtutorial.aem.page/, but how about production... how are these links generated for production websites?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @AEMWizard ,
a) Tutorial has us share a folder to helix@adobe.com. Is this the same process on production?
Yes you need to share the folder to helix@adobe.com for google drive.Even in case of sharepoint as document repository you need to Provide read,create ,update permission for all files under document repo. Earlier i checked the same with question with Adobe Employee's they stated that "We need sites selected permission only for the folder that contains the website . Reason is some cases adobe would write back to google or sharepoint site for example when they update the query-index.xlsx when something get published and needs to be indexed or when content is unpublished in that case they need to remove entry in query-index.xlsx file that resides in google drive/sharepoint
b) Github need not be Public.Its just recommended. But you need to give read,write access for Aem Code sync Application plugin in github. This is needed because this AEM Code sync plugin does automated testing of lighthouse score and writes to PR with results example.This bot is basically a helper to automate some deployments/testing as well as to deploy the code to edge server. The URL that you get is Edge Server url: s https://main--mysite--aemtutorial.aem.page/ For PRoduction you will generate a similar url with your branch and repo name however on top you can map the CDN followed by DNS URL.
Hope this helps.
Regards,
Ganthi
Hi @AEMWizard ,
a) Tutorial has us share a folder to helix@adobe.com. Is this the same process on production?
Yes you need to share the folder to helix@adobe.com for google drive.Even in case of sharepoint as document repository you need to Provide read,create ,update permission for all files under document repo. Earlier i checked the same with question with Adobe Employee's they stated that "We need sites selected permission only for the folder that contains the website . Reason is some cases adobe would write back to google or sharepoint site for example when they update the query-index.xlsx when something get published and needs to be indexed or when content is unpublished in that case they need to remove entry in query-index.xlsx file that resides in google drive/sharepoint
b) Github need not be Public.Its just recommended. But you need to give read,write access for Aem Code sync Application plugin in github. This is needed because this AEM Code sync plugin does automated testing of lighthouse score and writes to PR with results example.This bot is basically a helper to automate some deployments/testing as well as to deploy the code to edge server. The URL that you get is Edge Server url: s https://main--mysite--aemtutorial.aem.page/ For PRoduction you will generate a similar url with your branch and repo name however on top you can map the CDN followed by DNS URL.
Hope this helps.
Regards,
Ganthi
And so, how does https://main--mysite--aemtutorial.aem.live turn into https://www.mywebsite.com
Views
Replies
Total Likes
Hi @AEMWizard
If you want to rely on Adobe CDN then contact adobe to do domain mapping.
If you have your CDN then map it to live domain , here : https://www.aem.live/docs/byo-cdn-setup
Okay so contacting Adobe can reference my AEM Edge Delivery Service with the free Adobe Fastly CDN?
Views
Replies
Total Likes
yes but EDS is not free the cost is based on usage, so please check with Adobe about license and cost.
Views
Likes
Replies