Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- Locally, after making changes to fragments, I can promote those changes using the command
npm run import
. - Is there a similar way to promote code through the CLI?
Environment
- Liferay PaaS
Resolution
- The CLI tool cannot build fragments.
- Instead, fragments should be built locally using
npm run compress
- Then added to the liferay/configs/environment/deploy folder in your local repo before pushing the changes to GitHub using the following steps:
- Add the fragment to the liferay/configs/environment/deploy folder in my local repo
- Push the changes to GitHub
- Deploy the build to my environment
- Check that the fragment is present
Additional Information
- For more information, see our documentation on Updating Fragments and Deploying Themes, Portlets, and OSGi Modules.
Contenido exclusivo para suscriptores.
Una Suscripción Enterprise de Liferay proporciona acceso a más de 1.500 artículos que incluyen las mejores practicas, diagnóstico de problemas y otras soluciones útiles. Inicia sesión para tener un acceso completo.
Inicia sesión