mirror of
https://github.com/only-cli/oc.git
synced 2026-09-15 10:40:56 +02:00
only-cli
e8f2b6172d
All three providers render their own docs search client-side, so distilling the search page yields only nav chrome. Microsoft Learn is the exception underneath: its public RSS search endpoint serves real results as a feed, which the engine already renders (same route as Stack Overflow). AWS and Google Cloud expose search only as JSON (#3), so until the engine renders JSON their search goes through DuckDuckGo HTML with a baked-in site: filter, the same endpoint the duckduckgo.com CLI already relies on. Bing was tried first for that job and rejected: it silently drops the site: operator on some queries. Verified live: the Learn RSS endpoint returns titled results for "app service deploy"; the DuckDuckGo route returns real docs.aws.amazon.com pages for "lambda timeout" (it can answer with a rate-limit challenge under rapid-fire automated use, noted in README).
10 lines
483 B
JSON
10 lines
483 B
JSON
{
|
|
"domain": "cloud.google.com",
|
|
"commands": {
|
|
"docs": { "open": "https://docs.cloud.google.com/{product}/docs", "args": ["product"] },
|
|
"page": { "open": "https://docs.cloud.google.com/{product}/docs/{page}", "args": ["product", "page"] },
|
|
"gcloud": { "open": "https://docs.cloud.google.com/sdk/gcloud/reference/{command}", "args": ["command"] },
|
|
"search": { "open": "https://html.duckduckgo.com/html/?q=site%3Acloud.google.com+{query}", "args": ["query"] }
|
|
}
|
|
}
|