Move render.yaml to repo root so Render detects the Blueprint - #3
Merged
Conversation
Render only looks for render.yaml at the repository root, not in subdirectories,
so deploy/render.yaml was invisible ("Blueprint file render.yaml not found").
Relocate it to the root (its dockerfilePath/dockerContext are already root-relative,
so service builds are unaffected) and update the README path reference.
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
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.
Render only detects
render.yamlat the repository root, sodeploy/render.yamlwas not found. Moves it to the root (internaldockerfilePath/dockerContextare already root-relative, so both service builds are unchanged) and fixes the README path. Deploys backend + frontend together.