Google Git
Sign in
apache / teaclave-website / refs/heads/master
commit6b1370687d0ff3850bb782e8d0eb1909c651d9bd[log] [tgz]
authorZhaofeng Chen <zfc@apache.org>Fri Jan 30 12:47:31 2026 +0000
committerzf <zfc@apache.org>Fri Jan 30 08:40:02 2026 -0500
tree93a66b4a5486f957278977f8401a2d3b2e00c317
parentcbb62c9bb305dfba0236b588b550ff2e01f06ba9 [diff]
ci: add manual deployment action
3 files changed
tree: 93a66b4a5486f957278977f8401a2d3b2e00c317
  1. .github/
  2. sgx-sdk-api-docs/
  3. site/
  4. tz-sdk-api-docs/
  5. .asf.yaml
  6. .dockerignore
  7. .gitignore
  8. Dockerfile
  9. LICENSE
  10. NOTICE
  11. README.md
README.md

Apache Teaclave™ Website

The official website for Apache Teaclave™, generated with the Docusaurus static site generator. This repository contains the source code and configuration for the Teaclave project website, including documentation for Teaclave TrustZone SDK, Teaclave SGX SDK, and related components.

Quick Start

Building the Website

  1. Build the Docker container:

    docker build . -t website

  2. Run the container and build the site:

    docker run -it --rm -v $(pwd):/app/repo website /bin/bash
cd site
make build

Deployment (CI/CD)

Deployment is handled by GitHub Actions:

  1. Merge a PR (or push to master) → the Deploy Staging workflow runs and updates the asf-staging branch.
  2. Verify the staging site.
  3. Promote to production → In the repo, go to Actions → “Promote Staging to Production” → Run workflow. This updates asf-site with the content of asf-staging.

For workflow details and architecture, see .github/workflows/README.md.

Manual deployment from a local build (e.g. make staging / make site in site/) is still supported; see site/Makefile.

Website URLs