chore: add fly.toml for deployment configuration#3
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a83f33c4e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [build] | ||
|
|
||
| [http_service] | ||
| internal_port = 8080 |
There was a problem hiding this comment.
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 👍 / 👎.
1 participant
Adds fly.toml to complete build_readiness score from 0.8 to 1.0.
Repo already has Dockerfile, Makefile, and .env.example. This adds the missing deploy configuration for Fly.io.