Learn more about operations work on Aptible - with minimal downtime and rollbacks
backup
: Creates a database backupconfigure
: Sets the configuration for an appcopy
: Creates a cross-region copy database backupdeploy
: Deploys a Docker image for an appdeprovision
: Stops all running containers and deletes the resourcesexecute
: Creates an ephemeral SSH session for an applogs
: Streams logs to CLImodify
: Modifies a database volume type (gp3, gp2, standard) or provisioned IOPS (if gp3)provision
: Provisions a new database, log drain, or metric drainpurge
: Deletes a database backuprebuild
: Rebuilds the Docker image for an app and deploys the app with the newly built imagereload
: Restarts the database in place (does not alter size)replicate
: Creates a replica for databases that support replication.renew
: Renews a certificate for an app endpoint using Managed HTTPS.restart
: Restarts an app or databaserestore
: Restores a database backup into a new databasescale
: Scales a service for an appscan
: Generates a security scan for an appbefore_release
commands cannot be rolled back (unless you design your migrations to roll back on failure, of course!). We strongly recommend designing your database migrations so that they are backwards compatible across at least one release. This is a very good idea in general (not just on Aptible), and a best practice for zero-downtime deployments (see Concurrent Releases for more information). aptible operation:cancel
command.
How do I access Operation Logs?
aptible operation:logs
command
How do I access Activity Reports?
Why do Operation Failures happen?