liferay-logs

Streams Liferay Docker container logs via Docker Compose commands.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/gweone/agent-plugins --skill liferay-logs-gweone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liferay-logs
Source: https://github.com/gweone/agent-plugins/tree/main/plugin/sharpps-liferay/skills/liferay-logs
Command: npx skills add https://github.com/gweone/agent-plugins --skill liferay-logs-gweone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working with Liferay in Docker need to monitor container output to confirm deployments, catch startup errors, and watch module activation, but manually recalling the right docker logs commands and interpreting raw output is repetitive and error-prone. ## Core Features & Use Cases - Live Log Streaming: Follows the liferay-dev container output in real time using docker compose logs with a configurable tail length. - Snapshot Inspection: Captures the last 200 lines of container logs without following, useful for quick status checks. - Event Interpretation: Highlights key log events such as server startup completion, successful bundle deployment, and ERROR or FAILED lines so issues surface immediately. - Use Case: After deploying a new OSGi module, ask to watch the Liferay logs and get a live stream with deployment success or failure clearly flagged. ## Quick Start Show me the live logs from the Liferay Docker container and tell me when the server finishes starting up.

Frequently Asked Questions about liferay-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view Liferay Docker container logs?

Run docker compose logs liferay-dev --tail=100 --follow for a live stream, or docker logs liferay-dev --tail=200 for a one-time snapshot. The skill chooses the right command based on whether you want continuous monitoring or a quick check.

How to monitor Liferay deployment in Docker logs?

Follow the container logs and watch for the STARTED marker followed by a bundle name, which confirms a module deployed successfully. The Server startup in message indicates the full Liferay startup sequence has completed.

What is the difference between docker logs and docker compose logs?

docker compose logs liferay-dev --follow streams output through the Compose project context, while docker logs reads directly from the named container. Both work here; the skill uses Compose for live streams and plain docker logs for snapshots.

Why is there no output in my Liferay container logs?

Empty or stalled log output usually means Liferay is still starting up, which can take several minutes on first launch. Keep the stream following and wait for the Server startup in message before assuming something is wrong.

How do I find errors in Liferay Docker logs?

Scan the log stream for lines containing ERROR or FAILED, which indicate deployment or runtime problems. The skill surfaces these lines prominently so you can act on them without reading the entire output.