chore: drop stale render.yaml, document Railway as the deploy target - #34
Merged
Conversation
The app deploys on Railway from main, but the repo still carried a Render blueprint from the publish workflow and no mention of Railway anywhere. The stale file was actively misleading about where production runs. Removes render.yaml, documents the real deploy target in the README, and adds the W35 changelog covering this and the FRINK endpoint migration.
|
This PR was not deployed automatically as @prayaslashkari does not have access to the Railway project. In order to get automatic PR deploys, please add @prayaslashkari to your workspace on Railway. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #33.
While checking whether the backend needed an endpoint change,
render.yamlled me to conclude production runs on Render. It doesn't — it's on Railway. The file is a leftover from the publish workflow and had been tracked onmainand every active branch, ready to mislead the next person or agent the same way.render.yaml. Nothing builds from it. Recoverable from history (411f9dd) if the Render setup is ever revived.## Deploymentsection: Railway, frommain, config in the Railway dashboard rather than the repo (there's norailway.jsonornixpacks.tomlhere).docs/changelog/2026-W35.mdcovering this plus the FRINK →apps.okn.usmigration from fix(endpoints): move SPARQL endpoints from FRINK to apps.okn.us #33. Previous changelog file was W11, so this starts a new week file.npm run buildclean.Not touched:
public/_redirects, a Netlify artifact from a still earlier host. Harmless, but the same category of confusion if you want it gone too.