Hey there! We've found the following might help you get unblocked faster:

• 🧵 Frontend Deployment Issues After Supabase Edge Functions Integration - Site Not Loading

• 📚 Deploy a Ruby on Rails App

• 🧵 Deployment Auto-Start Issue - Build Succeeds but No Logs Until Manual Restart

If you find the answer from one of these, please let us know by solving the thread!

Hello,

We did not add that, either you or someone on your team has added it.

Best,

Brody

Thanks Brody. Is it safe to remove that service called Rally? Not sure why it’s there.

The Rally service appeared when I added my git repository “Rally” to the APTA_cron_service to source repo

Hey, it's safe to remove the extra service, given that it was never intended to be there and nothing seems to reference it in any way. I also noticed that there are no reference connections between your other services, you may want your application services to reference your database service using the private url (DATABASE_URL) to eliminate egress.

Thank you for pointing out that I want my application services to reference my database service using the private url (DATABASE_URL) to eliminate egress. Couple follow up questions:

1. Do I have this issue in both staging and production, or just production?
2. Can you be more specific on where i would make that change?

Thank you so much for your support!

Ross

Hey, I am not sure if this issue is also present in other environments as I don't have the ability to look into your project. You will have to reference them using ${{service_name.DATABASE_URL}} in the variables tab. I have attached an example below.

I have a staging project and a production project in Railway. Below are the configurations. I want to make sure I am using the internal database URLs to connect my applications to their respective databases. How do I ensure that is the case?

Hey, in your screenshots above, in your production may have the correct DATABASE_URL value but it is not referenced. Make sure that the value you have set is not the raw DATABASE_URL itself but a reference to that variable which should be ${{Rally Production Database.DATABASE_URL}}, if this is your database's name in the production environment. In my case, this is just ${{Postgres.DATABASE_URL}}, since my database service is called Postgres.

The same can also be said in your staging environment, in this case I have seen that you are for some reason using shared (global) variables since there is a globe icon next to your DATABASE_URL, this shouldn't be done either. Your other two services (APTA_Cron_Service_Staging and CNSWPL_Cron_Service_Staging) are referencing the database correctly, as seen by the arrows going to your database service. Make sure that your DATABASE_URL is a reference to ${{Rally STAGING Database.DATABASE_URL}} and not to a global variable.