---
title: "Fly Answers Questions - Suspend, Resume, Restart and Redis"
description: "Fly’s answers clarify how to stop an application temporarily, restart instances, configure minimum capacity, use Redis, and invoke the CLI. The fly suspend command reduces an app’s instance count to zero while preserving its status and settings; fly resume first restores one instance, checks it, and then redeploys from the previous configuration. By contrast, fly restart restarts each instance in place without triggering a deployment, while applications cannot set a minimum instance count of zero except by suspending. Fly’s Redis implementation does not support Pub/Sub, scripting, or Geo commands, and flyctl now creates a symlink to the shorter fly command as migration toward the latter continues with script compatibility in mind."
---

# Fly Answers Questions - Suspend, Resume, Restart and Redis

[Fly.io](https://yomu.fyi/company/fly-io) · Oct 30, 2020

**Type:** Explainer

## Summary

Fly’s answers clarify how to stop an application temporarily, restart instances, configure minimum capacity, use Redis, and invoke the CLI. The fly suspend command reduces an app’s instance count to zero while preserving its status and settings; fly resume first restores one instance, checks it, and then redeploys from the previous configuration. By contrast, fly restart restarts each instance in place without triggering a deployment, while applications cannot set a minimum instance count of zero except by suspending. Fly’s Redis implementation does not support Pub/Sub, scripting, or Geo commands, and flyctl now creates a symlink to the shorter fly command as migration toward the latter continues with script compatibility in mind.

## Context

The answers address questions about temporarily parking Fly applications without destroying configuration, distinguishing suspension from restarting, understanding Redis command limitations, setting zero instances, and using the fly versus flyctl CLI names.

## Approach / What changed

The guidance contrasts fly suspend, fly resume, and fly restart behavior; documents unsupported Redis command groups; explains that zero instances require suspension; and describes the CLI’s symlink-based migration from flyctl to fly.

## Takeaways

- fly suspend reduces an application’s instance count to zero while retaining its status and settings; fly resume restores one instance initially and then redeploys using the previous configuration.
- fly restart restarts each application instance in place and does not trigger a deployment. Fly applications cannot normally set their minimum instance count to zero.
- Fly’s Redis implementation does not support Pub/Sub, Redis scripting, or Geo-based commands. Installing flyctl creates a symlink to fly, so either command can be used.

**Tags:** [Fly.io](https://yomu.fyi/topic/fly-io), [Redis](https://yomu.fyi/topic/redis)

- Source: [Fly.io](https://fly.io/blog/fly-answers-questions-suspend-resume-restart-and-redis)
- Source URL: https://fly.io/blog/fly-answers-questions-suspend-resume-restart-and-redis
- Ingested by Yomu: 2026-09-03T00:00:54.513Z

[Read original post](https://fly.io/blog/fly-answers-questions-suspend-resume-restart-and-redis)