/content/DemoSite
/content/dam/DemoSite
/apps/DemoSite
/apps/DemoSiteService
/apps/wcm
1. Create the package click on Create Package
Fill in the following details
Package Name: DemoSite
Version: 0.1
Leave group as default
Click on OK
Then click on Edit
2. General TabAdd your description, and a Thumbnail. Thumbnails are good to quickly recognise the different packages.
3. Filters Tab
Version: 0.1
Leave group as default
Click on OK
Then click on Edit
2. General TabAdd your description, and a Thumbnail. Thumbnails are good to quickly recognise the different packages.
3. Filters Tab
Enter /content/DemoSite into Root path: and click on Done.
repeat for the remaining directories:
/content/dam/DemoSite
/apps/DemoSite
/apps/DemoSiteService
/apps/wcm
You can add rules to specifically exclude directories and include sub directories of excluded directories here as well.
4. Dependencies TabIt is important to keep an eye upon which version of CQ5, uncluding service packs that the package has been built and tested with. There are differences between the varying versions, and this can be useful later on to track what may have gone wrong between them.
As of Adobe CQ5-5.5.0, Package Depends on and Replaces is simply a text list. Although useful, and an item that should be filled in to make maintenance easier, it does not enforce replacement, nor dependency.
5. Advanced Tab
The Advanced Tab allows you to put your details in, so that anyone installing the package in future has an easy reference for whom to contact.
If you need Admin priviliges or a restart, check the check boxes.
IMPORTANT:
Set the AC Handling to what your default should be.
(From http://dev.day.com/docs/en/cq/current/core/how_to/package_manager.html)
IgnoreIgnores the packaged access control and leaves the target unchanged.OverwriteApplies the access control provided with the package to the target. This also removes existing access control.MergeTries to merge access control provided with the package with the one on the target. This is currently not fully supported and behaves like Overwrite for existing ACLs. ACLs not in the package are retained.MergePreserveTries to merge access control provided with the package with the one on the target. This is currently not fully supported and behaves like Ignore for existing ACLs. ACLs not in the package are retained.ClearClears all access control on the target system.
By default we pick Overwrite to force ACL settings in.
6. Screenshots TabThis is where you can place any images that you wish to keep with the packages. We generally have no use for this feature. Please comment below if there is a good use case for them.
Click on Save, and your settings are complete.
7. Building the package
Click on the build button.
You can now download the package using the download button. You will get a zip file, which you can then deploy onto another cq5 instance.
repeat for the remaining directories:
/content/dam/DemoSite
/apps/DemoSite
/apps/DemoSiteService
/apps/wcm
You can add rules to specifically exclude directories and include sub directories of excluded directories here as well.
4. Dependencies TabIt is important to keep an eye upon which version of CQ5, uncluding service packs that the package has been built and tested with. There are differences between the varying versions, and this can be useful later on to track what may have gone wrong between them.
As of Adobe CQ5-5.5.0, Package Depends on and Replaces is simply a text list. Although useful, and an item that should be filled in to make maintenance easier, it does not enforce replacement, nor dependency.
5. Advanced Tab
The Advanced Tab allows you to put your details in, so that anyone installing the package in future has an easy reference for whom to contact.
If you need Admin priviliges or a restart, check the check boxes.
IMPORTANT:
Set the AC Handling to what your default should be.
(From http://dev.day.com/docs/en/cq/current/core/how_to/package_manager.html)
IgnoreIgnores the packaged access control and leaves the target unchanged.OverwriteApplies the access control provided with the package to the target. This also removes existing access control.MergeTries to merge access control provided with the package with the one on the target. This is currently not fully supported and behaves like Overwrite for existing ACLs. ACLs not in the package are retained.MergePreserveTries to merge access control provided with the package with the one on the target. This is currently not fully supported and behaves like Ignore for existing ACLs. ACLs not in the package are retained.ClearClears all access control on the target system.
By default we pick Overwrite to force ACL settings in.
6. Screenshots TabThis is where you can place any images that you wish to keep with the packages. We generally have no use for this feature. Please comment below if there is a good use case for them.
Click on Save, and your settings are complete.
7. Building the package
Click on the build button.
You can now download the package using the download button. You will get a zip file, which you can then deploy onto another cq5 instance.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.