restarting-netalertx-services

Start NetAlertX services using internal scripts in /services: run start-backend.sh, start-php-fpm.sh, start-nginx.sh, and start-crond.sh sequentially from within the container. Stop services by terminating their processes. This Skill orchestrates these operations without requiring docker exec or external software.

Yes. This Skill lets you restart individual services—nginx, php-fpm, backend, and cron—on demand from inside the container. Each service has its own start script under /services, allowing selective restarts without container interruption.

Monitor running services using pgrep to check for active processes. This Skill provides status verification commands to quickly identify which backend, frontend, nginx, php-fpm, and cron services are active inside the devcontainer.

Use script-driven orchestration from within the container rather than docker exec commands. This Skill relies on internal /services scripts to start, stop, restart, and monitor all NetAlertX services, reducing risk to the host environment while keeping operations unified and repeatable.

No external software is required. This Skill operates entirely within the devcontainer environment, using built-in scripts and standard process management commands like pgrep to orchestrate backend, frontend, nginx, php-fpm, and cron services.