Ship a .sc.yml with only the endpoint, and document why #13

Merged
geusebio merged 1 commit from chore/drop-sc-yml into main 2026-08-03 18:57:26 +00:00
Owner

The project had a .sc.yml restating what detection already works out (app: example-app), which hid the thing this reference app exists to demonstrate. It now sets only the endpoint:

endpoint: http://127.0.0.1:7500

app and deployment stay out because sc gets 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 bare sc deploy in 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.yml existed the same run actually printed (from .sc.yml) — the guide was describing detection this project was not exercising. Noted in "How this was verified".

The project had a `.sc.yml` restating what detection already works out (`app: example-app`), which hid the thing this reference app exists to demonstrate. It now sets **only** the endpoint: ```yaml endpoint: http://127.0.0.1:7500 ``` `app` and `deployment` stay out because `sc` gets 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 bare `sc deploy` in 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.yml` existed the same run actually printed `(from .sc.yml)` — the guide was describing detection this project was not exercising. Noted in "How this was verified".
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/someones.computer_example_app!13
No description provided.