Deployment on Railway - Connection Issues and Best Practices
urosh-appify
TRIALOP

a year ago

Dear Railway Support Team,

I am experiencing issues deploying Discourse on Railway and would like to inquire about the platform's compatibility and best practices.

Current Setup:

  1. PostgreSQL service (separate instance)

  2. Redis service (separate instance)

  3. Discourse service (using Bitnami Discourse image)

Issue:

  • Unable to establish database connection despite correct environment variables

  • All logs are marked as errors, including welcome messages

  • Using Railway's internal DNS (monorail.proxy.rlwy.net) for service communication

Questions:

  1. Is Discourse officially supported on Railway?

  2. Are there any known successful deployments of Discourse on Railway?

  3. What is the recommended approach for deploying Discourse on Railway?

  4. Are there any specific networking requirements or limitations when running Discourse on Railway?

  5. Should we use Railway's internal DNS or direct IP addresses for service communication?

  6. Are there any specific environment variables or configurations that need to be set differently for Railway?

Additional Information:

  • Using Bitnami Discourse image

  • All services are in the same Railway project

  • Attempted using both private and proxy domains

  • Tried various environment variable combinations

Any guidance or documentation regarding Discourse deployment on Railway would be greatly appreciated.

Best regards,

1 Replies

urosh-appify
TRIALOP

a year ago

a00b21d9-e7f0-4f78-8d2c-462c8d1b1fd8


Loading...