Currently pkispawn deploys a subsystem by copying web application files (e.g. JS scripts, images, templates, web.xml, auth.properties) into Tomcat's webapps folder. This creates a maintenance issue. Suppose during upgrade the layout/content of these files has changed, the deployed files will need to be migrated or the web application will need to be redeployed.
It is possible to deploy without copying the files by configuring the docBase parameter in the context.xml of each subsystem to point directly to the installed files, for example:
<Context docBase="/usr/share/pki/webapps/ca"> </Context>
This way the changes will be handled automatically by RPM.
Design document: http://pki.fedoraproject.org/wiki/Customization#Direct_Deployment
Implemented for TPS:
Additional changes:
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2.3
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1070
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.