Here : https://github.com/AdobeDocs/experience-manager-65.en/blob/master/help/forms/developing/pdf-utilities.md

Without going too deep here, there were some issues in 6.3 where some ACL's got overridden (NPR-23208) and the reference-adjustment-service user didn't have jcr:read on /content. It's mentioned in the release notes https://helpx.adobe.com/ca/experience-manager/release-notes--aem-6-3-cumulative-fix-p...

Maven Archetype 22 only supports AEM 6.3.3.4+ https://github.com/adobe/aem-project-archetypehttps://github.com/adobe/aem-project-archetype/blob/master/VERSIONS.md NOTE : AEM 6.3 is fast approaching end-of-core-support in April 2020. If you're starting a new project, it's not advised to be starting o...

Why would you want to replicate that out of curiosity? Secondly, unless the hmac/master keys were physically copied from the filesystem (/crx-quickstart/launchpad/felix/bundle25/data) to this other instance day-0 then I wouldn't expect any cryptographic hash-functions to be able to sign. 

You will never be able to satisfy that requirement. The 'admin' user is a super user that cannot be modified. Note 'admin' and an 'Administrator' are NOT the same thing at all. Also seek to understand the WHY behind that requirement -- so so so many features require jcr:read on /home 

Personally I'd also add :  -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamp These will output Java garbage collection statistics to logs. Some of the most useful logs when things hit the fan. Allows you to visualize the Java heap state across time.

Webp is supported as part of a DynamicMedia/Scene7 license See :https://docs.adobe.com/content/help/en/experience-manager-64/assets/dynamic/imaging-faq.html It is not supported with the core AEM Assets product at this time.  See :https://docs.adobe.com/content/help/en/experience-manager-65/assets/ad...

If the custom tag is getting stripped it's likely happening from the XSS filter. /apps/cq/xssprotection/config.xml/libs/cq/xssprotection/config.xml NOTE : AEM 6.3 is fast approaching end-of-core-support in April 2020. 

That error message in-and-of itself isn't helpful. First validate the command you're using executes on command-line (removing AEM from the picture altogether)  Then, assuming you get the desired output from ImageMagick, apply that to the Command Line step in your Workflow.  Also FYI -- AEM 6.3 is fa...

I general -- a Move in AEM is a very expensive operation as any number of references and things need to be adjusted post move. Just be cognizant of that. If you're moving a lot of subtrees you may see some resource contention within the JCR. This article is a bit dated but conveys what you can do wi...