Skip to main content
Omeka Classic does not define its own lifecycle commands. Like every application plugin, an Omeka Classic stack is built, started, stopped, inspected, and rolled out with the core sitectl commands, which operate on whichever context is active: 
sitectl create omeka-classic   # scaffold the stack and its context
sitectl compose build          # build images
sitectl compose up -d          # start the stack
sitectl compose ps             # service status
sitectl compose logs -f        # follow logs
sitectl compose down           # stop the stack
sitectl deploy                 # pull updates and restart (rollout)
sitectl omeka-classic ... is reserved for Omeka Classic-specific operations — the API helpers and resource shortcuts. General lifecycle stays in the core CLI so the same operational contract applies to every stack. See sitectl create, sitectl compose, and sitectl deploy for the full lifecycle reference.