Exposing Nakama ports on Railway (7350 app + 7351 console) + updating config values?
elriando
HOBBYOP
2 months ago
Hi everyone,
I’m deploying Nakama on Railway and I can access the console on port 7351, but I’m confused about the public domains per port.
Questions:
How did you expose both 7350 (client API) and 7351 (console)? Did Railway give you one domain per port, or did you use a reverse proxy? I currently only see one public domain (7350).
How do you update the insecure defaults shown in the Nakama console (socket.server_key, session.encryption_key, console.signing_key, runtime.http_key, etc.)? Are you passing them via Railway environment variables (start command) or via a custom
config.yml?
Any concrete steps or a working example would be super helpful. Thanks!
Attachments
0 Replies