Configuring The Workspace For Distribution Bundles When you build a custom distribution bundle, you are packaging all of your stuff into a complete application, an application that you can spin up on any commodity server whether it is your local workstation, the dev/test/uat/prod tiers, or even on a cloud-based virtual server. Your application, though, is Liferay and Tomcat and your customizations and your configuration. So why do you need a custom distribution bundle? So you can commoditize your own servers, to use them to host your application. It's basically just "have a JVM" and you can spin up Liferay. Liferay doesn't give you a list of things you have to install, setup, configure, etc. That Liferay/Tomcat bundle you download to your workstation, expand, start and play with? That treats your local workspace as a commodity. We actually minimize work and cost when we can commoditize our servers rather than treating them as assets. A server isn't an asset, it is just a commodity we need to host our application. We are basically cultivating assets that need protecting and nourishing.Ĭontainerization showed us a different vision. Seriously, we invest so much time into purchasing servers, installing software, performing updates and maintenance, monitoring availability and downtime, etc. The rise of containerization though showed us the truth - servers are not assets as much as they are commodities. These deployments, though, tend to be manual efforts, sometimes face problems because of environmental issues, etc. In production, you're often concerned about keeping some nodes up during deployment so users don't face any downtime, so you juggle the nodes in the cluster to get them updated and back in the cluster as soon as possible. Why Do I Want A Custom Distribution Bundle?įollowing the classic model, the developer compiles the customizations into jars and wars, these are deployed and promoted through the environments, eventually to be deployed to production. The Maven-based workspace sports the same capabilities, you just use mvn instead of gradlew. When you have your Gradle-based workspace, the simple command gradlew distBundleZip or gradlew distBundleTar can build you a prepackaged Liferay bundle using Liferay CE or DXP, Tomcat, your custom modules as well as your configuration for the targeted environment. The Liferay Workspace comes with a great build option that I'm not sure developers know about and/or use - distribution bundles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |