You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,14 +107,13 @@ The site is published by **ASF infrastructure**, not GitHub Pages. On every push
107
107
```yaml
108
108
publish:
109
109
whoami: publish
110
-
hostname: magpie.apache.org
111
110
```
112
111
113
-
Production URL: **[magpie.apache.org](https://magpie.apache.org/)** (served at the apex root).
112
+
ASF infra serves the `publish` branch at the project's inferred hostname — `magpie-site` → **[magpie.apache.org](https://magpie.apache.org/)** (served at the apex root). The hostname must **not** be set explicitly via a `hostname:` field; asfyaml forbids naming your own `$project.apache.org` ("it has to be inferred to prevent abuse"), and doing so stops the site from publishing.
114
113
115
114
The site is built with `base: '/'` so all links and assets resolve against the apex domain. Set `SITE_BASE` / `SITE_URL` to preview under a subpath (e.g. GitHub Pages).
116
115
117
-
> One-time infra setup (outside this repo): the `magpie.apache.org` hostname and its TLS must be registered with ASF Infra, and the `publish` branch created on first CI run.
116
+
> One-time infra setup (outside this repo): for a brand-new project, ASF Infra may still need to provision DNS/TLS for `magpie.apache.org` before the inferred hostname resolves.
0 commit comments