fix: restore Fly deployment - #54
Merged
Merged
Conversation
Prompt: approve the fixes Co-authored-by: Codex <codex@openai.com>
lewxdev
marked this pull request as ready for review
August 15, 2026 01:45
drewradcliff
approved these changes
Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what changed
0.0.0.0:3000why
the latest Fly deployment was blocked by a TypeScript error in the new minimap. the running release also reported a misleading
localhostaddress even though Fly requires a wildcard listener.impact
the production image can build again, and the server's configured address now matches Fly's routing contract.
validation
BASE_URL=https://mmmines.fly.dev npm run buildnpm run lintgit diff --check