Migrate Node Chatbot to Railway

I’m moving my longtime F-List chatbot—built on Node.js, fchatlib, and the old Redis 2.x stack—from a self-hosted box to Railway. The code already lives on GitHub and the Railway build completes, but the service exits on launch because every Redis call is still pointed at 127.0.0.1 or a fixed LAN IP. Your job is to modernise those connections so the bot talks to Railway Redis through environment variables, then get the whole thing to boot, log in, and run exactly as it used to.

Key things to check once the refactor is in place:
• User interactions
• Command responses
• Automated tasks

I’ll give you repository access plus the current Railway logs that show where it dies. After you swap in the proper connection string, handle any auth nuances, and clean up legacy code that assumes an on-prem instance, confirm the login handshake on F-List succeeds and all three plugin behaviours above work without errors. The project does contain adult-themed role-play content, so you’ll need to be comfortable compiling and testing in that context.

Deliver the working commit (or pull request) that deploys cleanly on Railway, with concise notes on what changed and why, and I’ll take it from there.