Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure runtime container for Railway #230

Merged
merged 5 commits into from
Jan 15, 2025

Conversation

carlosantoniodasilva
Copy link
Member

@carlosantoniodasilva carlosantoniodasilva commented Jan 10, 2025

We're early-testing Railway as a platform integration, this adds detection for the Railway environment to report the runtime container as the Railway Replica ID.

It also refactors a bit the runtime container logic, and stops appending the render service ID to the API url when it's set to JUDOSCALE_URL, as we don't need that anymore.

Related:

We support it on the backend for legacy installations that migrate over
to `JUDOSCALE_URL` so they can keep using the same gems, but there's no
need to continue using the legacy URLs on new versions now.

If the app is setup with `JUDOSCALE_URL` it should just use that, if
it's setup with the legacy render support nothing changes, they report
the Render service ID as their token.
Keep order a bit more consistent across libraries, and most common
platform likely first.

Just check for the ENV containing one of the expected keys to determine
which runtime container info to use.
@carlosantoniodasilva carlosantoniodasilva marked this pull request as ready for review January 10, 2025 19:05
@carlosantoniodasilva carlosantoniodasilva merged commit bbcebf4 into main Jan 15, 2025
130 checks passed
@carlosantoniodasilva carlosantoniodasilva deleted the ca-config-runtime-container branch January 15, 2025 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants