Operations

Page	What it covers
CLI reference	Every bin/magento nebula:* command with its options
Caching and production mode	What is cached where, and the deploy sequence
Logs and monitoring	The messages Nebula writes, where they land, and which ones to alert on
Security	Sign-in and two factors, ACL enforcement, request protection, CSP, and the checklist to run before going live
Quality gates	The checks the project runs, and which of them block a merge
Known limitations	What is parked, deferred, or done differently from stock

The deploy sequence

composer install --no-dev
bin/magento setup:upgrade --keep-generated
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento nebula:compile
bin/magento cache:flush
cachetool opcache:reset                  # or reload PHP-FPM

nebula:compile is the one Nebula-specific step. setup:di:compile runs it for you at the end, so the explicit call is a safety net for pipelines that clean generated/ afterwards or skip di:compile. In production mode the manifest it writes is the only definition source, and because it is a plain PHP file that cache:flush does not touch, reset the opcache or reload PHP-FPM after it.