ci: fix git push auth with long GITHUB_TOKEN
GITHUB_TOKEN now uses a new format that is about 377 characters long.
Both deployment jobs encode it with plain base64, whose output is
wrapped at 76 columns. The newlines embedded in the http.extraheader
value make the header malformed, so GitHub resets the request and the
push fails with:
fatal: unable to access 'https://github.com/apache/teaclave-website.git/':
HTTP/2 stream 1 was not closed cleanly before end of the underlying stream
Encode the credentials with base64 -w0 so that they stay on a single
line. While at it, use printf instead of echo -n, as the former does
not interpret escape sequences.
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.
Build the Docker container:
docker build . -t website
Run the container and build the site:
docker run -it --rm -v $(pwd):/app/repo website /bin/bash cd site make build
Deployment is handled by GitHub Actions:
master) → the Deploy Staging workflow runs and updates the asf-staging branch.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.