Update Results page (#172)

* Cleans up navigation and content

* Explains how to use results

* Cleans up content

* Includes _site again

* Adds missing parent header

* Excludes _site

* Lists folder

* Stops using docker

* Reverts build to version before starts using Docker

* Fixes typo in env name

* Defines envs in script

* Avoids using env prefix

* Sets proper envs

* Reverts to Docker again

* List folders after Docker ends

* Performs all git operations in Docker

* Puts back Docker

* Cleans up workspace and add missing git user data

* Uses local git config

* Builds with Docker and moves content out of Docker

* Uses full path

* Uses context path

* Maps dedicated folder to store generated site

* Uses Dockerfile with dedicate UID

* Uses proper dockerfile syntax in pipeline

* Moves building site into pipeline

* Defines proper WORKSPACE env

* Moves building commands back to pipeline

* Uses proper GID

* Reverts to non-Docker build

* Stops installing ruby

* Pushes changed Gemfile.lock

* Adds remote refs where to push

* Adds branch to push

* Shows bundler version

* Show git changes

* Restores Gemfile.lock

* Uses checkout to restore file

* Adds ToC

* Cleans up page

* Cleans up page
17 files changed
tree: ffccff819f23a330dcd49623ccd3ec050d49feb4
  1. source/
  2. src/
  3. .asf.yaml
  4. .gitignore
  5. _config.yml
  6. docker-build.sh
  7. Gemfile
  8. Gemfile.lock
  9. Jenkinsfile
  10. PLACEHOLDER
  11. pom.xml
  12. README.md
README.md

Apache Struts Website

This project is used to update the main Apache Struts website http://struts.apache.org/
See the update website documentation on how to push changes online. However as ASF is using aggressive caching, for a while one still may need to forcely reload the page (CMD+R or Shift+F5) after changes.

Site is generated by Jekyll and uses pure html either markdown format. To test website locally you can use the below command:

bundle exec jekyll serve -w --trace --host 0.0.0.0

or you can use Docker (please install it first) with one of the provided scripts:

./docker-run.fish

when running fish-shell, or:

./docker-run.sh

when running Bash or Sh.

The continuously generated website can then be accessed at http://localhost:4000

All pages are generated into the content folder.

There are two scripts used to build the image but this should be used only when Dockerfile was modified.

Some redirect rules are configured in source/.htaccess file.