docs: Update Redis connection string instructions for Railway

[qbitdoge]

What

Updated the Railway Redis and Postgres connection string instructions:

• Changed DATABASE_URL to use ${{Postgres.RAILWAY_PRIVATE_DOMAIN}}
• Updated REDIS_URL to use ?family=0 to support both IPv6 and IPv4 connections.
• Adjusted instructions to reflect the new REDIS_URL configuration

Why

Railway does not support IPv4 private networking, so users need clearer guidance to enable IPv6. Additionally, the egress fee note ensures users are aware of potential costs when using public endpoints.

How

Edited the relevant section in the documentation for clarity and conciseness.

Testing

Changes are text-only and have been reviewed for accuracy.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 62cb853

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@qbitdoge is attempting to deploy a commit to the medusajs Team on Vercel.

A member of the Team first needs to authorize it.

[shahednasser]

Thank you for your contribution!

Referring to this documentation, it says setting family=0 supports both IPv6 and IPv4 connections, so I think we should set it to that. Then we don't need to add the note about Redis.REDIS_PUBLIC_URL

Another thing: the REDIS_URL is set in two places (for worker and server environments). Can you update it there?

Also, it would be great if you can update DATABASE_URL as well to be ${{Postgres.RAILWAY_PRIVATE_DOMAIN}} as this Railway change (regarding fees) seem to apply to it as well.

[qbitdoge]

@shahednasser thanks so much for the feedback and suggestions.
I’ve addressed all the changes as requested.
Let me know if there’s anything else that needs adjustment.

[qbitdoge]

@shahednasser done! anything else?

[shahednasser]

LGTM thanks!

[waptik]

Putting this here as there was some error with postgres.
DATABASE_URL value should be changed to ${{Postgres.DATABASE_URL}} instead of ${{Postgres.RAILWAY_PRIVATE_DOMAIN}} because its value remains postgres.railway.internal instead of postgresql://postgres:xxxxxx@postgres.railway.internal:5432/railway
Another PR must be created to fix it

[shahednasser]

You're correct @waptik , when I used it in Railway's dashboard it showed me that the value was the full address but it wasn't. I'll open another PR to make the update

[waptik]

You're correct @waptik , when I used it in Railway's dashboard it showed me that the value was the full address but it wasn't. I'll open another PR to make the update

Can you turn your working architecture into template because i followed the guide and my server instance has been crashing because of index.html

My variables

ADMIN_CORS="https://${{RAILWAY_PUBLIC_DOMAIN}},https://${{RAILWAY_PRIVATE_DOMAIN}}"
AUTH_CORS="https://${{RAILWAY_PUBLIC_DOMAIN}},https://${{RAILWAY_PRIVATE_DOMAIN}}"
STORE_CORS="http://localhost:8000,https://docs.medusajs.com"
DATABASE_URL="${{Postgres.DATABASE_URL}}"
REDIS_URL="${{Redis.REDIS_URL}}?family=0"
JWT_SECRET="****************"
COOKIE_SECRET="****************"
PAYSTACK_API_KEY="****************"
NODE_ENV="production"
PORT="9000"
MEDUSA_ADMIN_EMAIL="me@email.xyz"
MEDUSA_ADMIN_PASSWORD="****************"
MEDUSA_ADMIN_ONBOARDING_TYPE="default"
RAILWAY_PUBLIC_DOMAIN_VALUE="https://${{RAILWAY_PUBLIC_DOMAIN}}"
DISABLE_MEDUSA_ADMIN="false"
MEDUSA_WORKER_MODE="server"

[shahednasser]

Thank you for your feedback, I would double check that you've followed every step, and if the error is still happening you can open an issue describing your error