Skip to content

DO NOT MERGE — fly.toml: min_machines_running 1->0 (Telegram webhook mode, Phase 3b) #463

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

Open
jlunder00 wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

DO NOT MERGE — fly.toml: min_machines_running 1->0 (Telegram webhook mode, Phase 3b) #463

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
9 changes: 6 additions & 3 deletions fly.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,12 @@ primary_region = "sjc"
force_https = true
auto_stop_machines = "suspend"
auto_start_machines = true
# bot long-polling requires a persistent connection — set to 0 once
# Telegram webhook mode ships (Phase 3b)
min_machines_running = 1
# Telegram webhook mode (Phase 3b) lets the machine itself sleep — the bot
# no longer needs a persistent long-polling connection when
# TELEGRAM_WEBHOOK_URL is set (see supervisord.conf [program:bot]).
# DO NOT MERGE this change until staging cold-start has been verified —
# see cc-context-store/tether/docs/infra/webhook-staging-verification.md
min_machines_running = 0

[env]
PYTHON_ENV = "production"
Expand Down
Loading