You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy this app as its own Railway service named `geoip`.
61
61
62
-
The service uses Hypercorn and binds both`0.0.0.0`and `::`by default so Railway's public deployment healthchecks and private networking can both reach it.
62
+
The service uses Hypercorn and binds to`0.0.0.0`by default. Wildcard values like `HOST=::`are normalized to the same single bind so Linux container runtimes do not fail with `address already in use`.
63
63
64
64
Use `/live` as the Railway deployment healthcheck path. `/health` remains a readiness endpoint and can return `503` until the MaxMind databases have been downloaded and loaded.
65
65
@@ -70,7 +70,7 @@ The service now starts serving `/live` immediately while the initial MaxMind boo
70
70
-`current_update_started_at`: when the active update began
71
71
-`last_update_error`: the latest refresh/bootstrap failure, if any
72
72
73
-
Railway environment variable values should be entered as raw values without wrapping quotes. For example, use `HOST=::`, not `HOST="::"`.
73
+
Railway environment variable values should be entered as raw values without wrapping quotes. For example, use `HOST=0.0.0.0`, not `HOST="0.0.0.0"`.
74
74
75
75
Railway logs will now include `geoipupdate` output, which makes it easier to confirm whether the MaxMind databases are actively downloading.
0 commit comments