Ship a .sc.yml with only the endpoint, and document why #13
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/drop-sc-yml"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The project had a
.sc.ymlrestating what detection already works out (app: example-app), which hid the thing this reference app exists to demonstrate. It now sets only the endpoint:appanddeploymentstay out becausescgets them from the checkout. The endpoint is the opposite case — no amount of looking at the repository reveals which platform you meant, so without that line a baresc deployin here goes to the hosted platform rather than a local stack. That is now the documented rule for the file: put in what detection cannot reach, leave out what it can.Also fixes a claim that had quietly gone stale: DEPLOYING.md's transcripts showed
Application: example-app (from directory), but while the old.sc.ymlexisted the same run actually printed(from .sc.yml)— the guide was describing detection this project was not exercising. Noted in "How this was verified".