Posts

Liferay: Upgrade Steps Audit

Image
  Liferay: Upgrade Steps Audit How to monitor and run repeatedly the Upgrade Steps  Introduction Liferay Upgrade Steps are designed to be run only once in order to perform some changes on the portal: database schema changes, data or configuration updates. But sometimes they can fail, or implementation logic might be not correct, and we might need to run them again after proper adjustments. Also, we need to see the state of each upgrade module to know exactly which upgrade steps were run already, and which ones are still pending.  Audit and Running Upgrades Check Available Upgrade Steps To check pending upgrade steps on the portal - you can run a Gogo Shell command: upgrade:check You should see the list of upgrade steps not executed yet in the output: Note : navigate to Control Panel → Gogo Shell or use the telnet terminal to run Gogo Shell commands.  Inspect a Specific Upgrade Module To inspect a specific module you can use a Groovy Script. Navigate to Control Panel ...
Post a Comment
Read more

Running Liferay as a Service

  Running Liferay as a Service How to run Liferay as a Service and make it auto-started on system reboot Introduction Sometimes servers hosting Liferay can be restarted. For a higher availability of the Liferay portal we need to make sure that Liferay is also started automatically during the system start. To achieve this - Liferay can be run as a service configured to auto-start. Configuration Define Liferay Service Configuration File To define a service for Liferay - create a liferay.service file inside /usr/lib/systemd/system directory as root user: sudo su  cd /usr/lib/systemd/system touch liferay.service nano liferay.service with the following content: [Unit] Description = Liferay Service After = network.target [Service] Type = forking User = user Group = user Environment = JAVA_HOME=[JAVA_HOME] Environment = CATALINA_PID=[LIFERAY-PATH]/tomcat[-x.x.x]/temp/tomcat.pid Environment = CATALINA_HOME=[LIFERAY-PATH]/tomcat[-x.x.x] Environment = CATALINA_BASE=[LIFERAY-PATH]/tomc...
Post a Comment
Read more

Tailwind and Flowbite in Liferay

Image
  Tailwind and Flowbite in Liferay Incorporating Tailwind Design System and Flowbite Components to Liferay 7.4 Introduction Liferay has its own design system based on Lexicon Design and Clay Components. For regular use cases, they can satisfy customer needs, and user interfaces can be built by using out-of-the-box components. But for more sophisticated user interfaces an external design system might be needed. TailwindCSS is one of the most popular CSS frameworks, and Flowbite is a components library based on TailwindCSS. This articles shows how to incorporate TailwindCSS / Flowbite to Liferay 7.4. TailwindCSS & Flowbite Integration Step 1: Standalone Configuration Before integrating to Liferay you can install & configure TailwindCSS and Flowbite separately. Note : but do this inside Lifeary workspace for future integration. Create a folder for TailwindCSS/Flowbite, e.g. lifedev-flowbite-loader. Install TailwindCSS TailwindCSS can be installed by leveraging Tailwind CLI, or...
Post a Comment
Read more