Many thanks @SantoshSai for the details. So, to implement the CLI approach you described, need all 4 below? And these are open source?Lighthouse CLI (Node.js)Puppeteer + Lighthouse Google PageSpeed Insights API Lighthouse CI (LHCI) –
Hi Experts,Could you kindly suggest if deployment independent for more number of pages ( more than 25 pages) same kind of lighthouse report can be generated? It will not be dependent upon AEMaaCS pipeline or deployment.If yes, kindly share in little details.Thanks in advance !!
Hi @Sb2512 ,Have you added the dependency correctly in your pom file. Please add below section in your pom and try give the build. <!-- https://mvnrepository.com/artifact/com.adobe.acs/acs-aem-commons-bundle --><dependency><groupId>com.adobe.acs</groupId><artifactId>acs-aem-commons-bundle</artifactI...
Hi @jayv25585659 ,
In general this should not happen, again on first hand please check what you are getting in author error log when published it. It must contain the cause.
Hi @neilwebbcbs ,Created replication user if by default having "everyone" group included it won't create any issue. This is by default comes with all users you create. Your extended section in replication agent would listen the domain with the user and flush the cache.
Hi @Rohan_Garg ,Please keep in mind, always check this kind of situation by following below steps:
- bypass the CDN and check the domain url, where it's landing.- Check the logs. Now, as per the description from your end, the domain is listening dispatcher in port 80, means it's http. Then it's reso...
Hi @kbitra1998 ,In general if the Author is connected with Dispatcher and project uses CDN, sitemap.xml also get behind it. Can you confirm with any other url also if that the same behavior you are seeing.