Best strategy for deploying portlet wars on to a production 7.2 instance?Best strategy for deploying portlet wars on to a production 7.2 instance?https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1205417902024-03-28T12:09:22Z2024-03-28T12:09:22ZBest strategy for deploying portlet wars on to a production 7.2 instance?Joel Schwabehttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1205417892021-01-08T23:57:33Z2021-01-08T23:31:04Z<p>I've recently upgraded from Liferay 6.2 to Liferay 7.2, and am in the
process of converting the automation processes for deployment.</p>
<p>I've looked through and read this article:<br />
<a href="https://help.liferay.com/hc/en-us/articles/360029134911-Managing-and-Configuring-Apps#managing-apps-in-production">https://help.liferay.com/hc/en-us/articles/360029134911-Managing-and-Configuring-Apps#managing-apps-in-production</a></p>
<p>With my manual deploys while in development, I haven't run into too
many issues just doing hot deploys by dropping the war file into the
deploy folder. Of course, stopping and starting the server is going to
be more fool-proof, but for a production environment that may have
dozens of portlets to start up, this could result in a large amount of downtime.</p>
<p>What is the best strategy for production deployment of portlets that
have not been specifically designed to be auto deployable? Are there
any clean up tasks I should be adding to my automation?<br />
<br />Thanks