# About the Build Liferay without Building Liferay category

**URL:** <https://discuss.liferay.com/t/about-the-build-liferay-without-building-liferay-category/984>\
**Category:** Build Liferay without Building Liferay\
**Tags:** workshop\
**Created:** [September 24, 2026, 8:28pm UTC](https://discuss.liferay.com/t/about-the-build-liferay-without-building-liferay-category/984 "2026-09-24T20:28:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnneDurey](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.liferay.com/annedurey/32/288_2.png) [@AnneDurey](https://discuss.liferay.com/u/AnneDurey)\
**Post date:** [September 24, 2026, 8:28pm UTC](https://discuss.liferay.com/t/about-the-build-liferay-without-building-liferay-category/984/1 "2026-09-24T20:28:04Z")

</div>

#### Build Liferay without Building Liferay

Presenters:

- Carlos Alvarez, Cloud Software Engineer, Liferay
- Greg Amerson, Staff Software Engineer, Liferay

Every Liferay developer knows the cycle: change a portlet or create a Client extension, rebuild the image, push to a registry, redeploy, watch the pods cycle. For a one-line tweak, you’ve burned ten minutes and a CI run. Good news: There’s a faster way.This session introduces the Overlay pattern in Liferay’s Cloud Native Experience (CNE): a workflow where your OSGi modules, client extensions and site initializers live in a cloud object store (S3 on AWS, GCS on GCP) and are copied into the Liferay pod at startup by a small init container — no image rebuild required. Your CI does a single copy. Your DXP image stays Liferay’s official image. Your iteration loop drops considerably.We’ll walk through the moving pieces (the overlay bucket, the init container, the overlay process in general), as well as show (live demo!) how to deploy different types of client extensions without rebuilding/redeploying the entire Liferay DXP application. We’ll also draw the honest line on what overlays are not for — the things that still need a rebuilt image.