Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a warning message to min_machines_running #1910

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Add a warning message to min_machines_running #1910

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion launch/autostop-autostart.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@
- /docs/apps/autostart-stop/
- /docs/launch/autostart-stop/
---

Your app can meet peak demand without keeping extra Machines running. Use autostop/autostart to automatically start and stop or suspend existing Machines based on incoming requests. Fly Machines are fast to start and stop, and you [don't pay for their CPU and RAM](/docs/about/pricing/#stopped-fly-machines) when they're in a `stopped` or `suspended` state.

Get all the details of [how Fly Proxy autostop/autostart works](/docs/reference/fly-proxy-autostop-autostart/).
Expand Down Expand Up @@ -52,9 +51,13 @@

To keep one or more Machines running all the time in your primary region, set `min_machines_running` to `1` or higher. If `min_machines_running = 1` and there's no traffic to your app, then Fly Proxy will stop Machines until eventually there is only one Machine running in your primary region. `min_machines_running` has no effect unless you set `auto_stop_machines` to `"stop"` or `"suspend"`.

<div class="important">
**`min_machines_running`:** This setting only maintains the specified minimum number of running Machines in your app's primary region. It has no effect on other regions where your app is deployed. If you need to maintain minimum running Machines in multiple regions, you'll need to manage those separately through other means like [`fly scale count`](https://fly.io/docs/flyctl/scale-count/#main-content-start).

Check failure on line 55 in launch/autostop-autostart.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.

Raw Output:
{"message": "[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.", "location": {"path": "launch/autostop-autostart.html.markerb", "range": {"start": {"line": 55, "column": 360}}}, "severity": "ERROR"}
</div>

### Maximum number of Machines running

There's no "maximum machines running" setting, because the maximum number of Machines is the total number of Machines in your app.

Check warning on line 60 in launch/autostop-autostart.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machines' instead of 'machines'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machines' instead of 'machines'.", "location": {"path": "launch/autostop-autostart.html.markerb", "range": {"start": {"line": 60, "column": 20}}}, "severity": "INFO"}

Fly Proxy autostop/autostart never creates or destroys Machines for you. The maximum number of running Machines is the number of Machines created for your app on launch, or using `fly scale count` or `fly machine clone`. For example, if you want to have a maximum of 10 Machines available to service requests, then you need to create 10 Machines for your app. Learn more about [scaling the number of Machines](/docs/apps/scale-count/).

Expand Down
Loading