Skip to content

drupal stack

Paulo Maia Carvalho edited this page May 20, 2026 · 1 revision

drupal-stack

Manage the full lifecycle of the Drupal Docker stack — start, stop, restart, status check, and destroy.

Usage

/drupal-stack
/drupal-stack action=stop
/drupal-stack action=status
/drupal-stack action=restart
/drupal-stack action=destroy

Parameters

Parameter Default Options
action start start, stop, status, restart, destroy
db mariadb mariadb, postgres, sqlite
php_port auto-detect any port number
db_port auto-detect any port number

Actions

start

Starts the stack if not already running. Equivalent to /drupal-serve but with explicit action semantics.

stop

Stops all containers in the Drupal stack without removing them:

docker compose -f /workspace/.piclaw/stack/docker-compose.yml stop

restart

Stops and starts the stack. Useful after config changes.

status

Shows which containers are running, their ports, and health state:

docker compose -f /workspace/.piclaw/stack/docker-compose.yml ps

destroy

Stops and removes all containers and volumes. Use this to reset the database completely.

docker compose -f /workspace/.piclaw/stack/docker-compose.yml down -v

The agent asks for explicit confirmation before running destroy.

Notes

  • Stack config lives at /workspace/.piclaw/stack/docker-compose.yml. Edit this file to customise the stack (PHP version, memory limits, etc.).
  • /drupal-serve is the quick-start alias for first-time setup. /drupal-stack is for ongoing management.

Related skills

  • drupal-serve — quick start for first-time setup
  • drupal-status — Drupal application status (separate from container status)
  • drupal-logs — view container and application logs

Clone this wiki locally