Limit Vercel deployment inputs - #5
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: 9cd4037f62
ℹ️ 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".
| .git/ | ||
| .pytest_cache/ | ||
| .venv/ |
There was a problem hiding this comment.
When vercel runs from a checkout after the documented local server has created flightops.db—or when a local .env exists—this new file becomes the active ignore list: Vercel documents that .vercelignore takes precedence over .gitignore. Because this list does not repeat the repository's .env and *.db exclusions, the CLI uploads local configuration and SQLite event data, potentially exposing data and reintroducing oversized uploads; preserve those patterns here.
Useful? React with 👍 / 👎.
1 participant
Excludes local raw/processed BTS data, training scripts, tests, and reports from serverless uploads while retaining the runtime API and portable JSON model. This reduced the production upload from more than 100 MB to 131 bytes after cache reuse. The deployed v0.2.0 health, metadata, and prediction endpoints were verified.