Skip to content
Projets

apache/spark-website has 141 GitHub stars and 252 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-20 00:08 UTC. Last push 2026-11-13.

Comment ces chiffres sont mesurés

Progression mesurée des étoiles

in 24h
0
in 7 days
Historique en cours
in 15 days
Historique en cours
in 1 month
Historique en cours

Variations nettes sur des périodes qui se chevauchent, pas des totaux quotidiens. Les mesures absentes restent vides. Les étoiles indiquent l’intérêt, pas la qualité.

À propos

Apache Spark Website

Données

README.md

Original

Apache Spark Main Website

This repository captures the main Apache Spark website located at https://spark.apache.org. The programming docs under https://spark.apache.org/docs/ are in the main Spark repo, not here. They are built separately for each release of Spark and then copied to the website under the docs/ directory.

Contributing

To contribute changes, build and test the site locally, then submit a pull request with your changes. Unless you are working through the release guide, you only need to commit changes to source files (typically Markdown). A GitHub Actions workflow will generate the corresponding HTML under site/ and push it for you.

Building the site locally

Building the site requires Ruby 3, Jekyll, and Rouge.

gem install bundler -v 2.4.22
bundle install
bundle exec jekyll serve

Building the site with Docker

The most reliable way to ensure a compatible environment is to use the official Docker build image from the Apache Spark repository.

If you haven't already, clone the Apache Spark repository. Navigate to the Spark root directory and run the following command to create the builder image:

docker build \
  --tag docs-builder:latest \
  --file dev/spark-test-image/docs/Dockerfile \
  dev/spark-test-image-util/docs/

Once the image is built, navigate to the spark-website root directory, run the script which processes the Markdown files in the Docker container.

.dev/build-docs.sh

Deploying to production

The website is deployed automatically by ASF Infra. The deployment configuration is tracked by .asf.yaml and is documented here.

One deployment detail that appears to be critical is the presence of the content symlink to site/. Even though ASF Infra is aware of Jekyll, we perhaps do not have the exact setup required for them to automatically use our Jekyll config to understand where the site content lives. Without the content symlink, the website will just show a plain directory listing of the files in this repo.