miren app disable
Hold every service of an app at zero instances
Disable turns an app off. Every service is held at zero instances: running sandboxes shut down, scheduled tasks pause, and visitors get a 503 holding page. The app is frozen until you enable it: deploys, rollbacks, and config changes are refused. The app keeps its versions, routes, environment, disks, and addons, so miren app enable brings it back as it was. Task runs already in progress finish, and addons keep running.
Disabled is an explicit state, so miren app list and miren app status report it as such rather than as an app that failed to start.
miren app run keeps working, which leaves room for a backup or a migration while the app is off. Scheduled tasks don't fire while the app is disabled, and enabling it resumes the schedule from that moment without running the ticks it missed.
To show visitors a holding page while the app keeps running, for a migration for example, put its routes into maintenance with miren route down instead.
Usage
miren app disable [flags]
Flags
--reason, -r— Why the app is disabled, shown by app status
Config Options
--cluster, -C— Cluster name--config— Path to the config file
App Options
--app, -a— Application name--dir, -d— Directory to run from (default:.)
Global Options
--options— Path to file containing options--server-address— Server address to connect to (default:127.0.0.1:8443)--verbose, -v— Enable verbose output
Examples
Disable an app:
miren app disable -a myapp --reason "Moved to the new cluster"