Skip to content

chore: add fly.toml for deployment configuration #3

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

Merged
saagpatel merged 1 commit into from
Mar 29, 2026
Merged

chore: add fly.toml for deployment configuration #3

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
16 changes: 16 additions & 0 deletions fly.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# fly.toml — Fly.io deployment configuration
# Update the app name to match your registered Fly.io app before running `flyctl deploy`
app = "slack-incident-bot"
primary_region = "sjc"

[build]

[http_service]
internal_port = 8080
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Mar 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Align Fly internal port with app listen port

internal_port is set to 8080, but this service listens on config.port whose default is 3000 (src/config.rs), and the container is also configured around port 3000 (Dockerfile EXPOSE 3000 and healthcheck on localhost:3000). Because this fly.toml does not set PORT=8080, Fly will proxy to a port the app is not listening on, causing failed health checks and unreachable HTTP endpoints after deployment.

Useful? React with 👍 / 👎.

force_https = true
auto_stop_machines = "stop"
auto_start_machines = true
min_machines_running = 0

[[vm]]
size = "shared-cpu-1x"
Loading