Skip to content

Configure staging for website previews - #109

Merged
tisonkun merged 1 commit into
trunkfrom
codex/site-preview
Sep 14, 2026
Merged

tisonkun merged 1 commit into
trunkfrom
codex/site-preview

Conversation

@tisonkun

Copy link
Copy Markdown
Member

Configure ASF staging for generated site/<name>-staging branches, served at https://steve-<name>.staged.apache.org. The whoami: asf-staging guard keeps source branches from being staged; the existing production Pelican configuration is unchanged.

This prepares the website rewrite for review before production deployment. The follow-up website PR will add the build workflow and include .asf.yaml in its generated output before pushing that output to a staging branch. This configuration alone does not build a site or automatically preview pull requests.

ASF staging configuration is branch-specific. Merging this first lets subsequent source branches inherit it; generated output branches must also contain the configuration.

Validation:

  • Full ASF schema validation with infrastructure-asfyaml at c10410aed8ea066e48826fc4bae0f9cf1dfe9025.
  • Dry-run staging routing: site/website-staging maps to https://steve-website.staged.apache.org; asf-staging maps to the default staging domain; trunk, codex/site-preview, site/website, and asf-site do not stage.
  • uv run ruff format ., uv run ruff check --fix ., and uv run mypy --ignore-missing-imports . passed in v3/.
  • git diff --check passed.

@tisonkun
tisonkun merged commit dc84b4c into trunk Sep 14, 2026
2 checks passed
@tisonkun
tisonkun deleted the codex/site-preview branch September 14, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant