Drop redundant intro lines under Why StormCrawler and Get started headings
1 file changed
tree: e2c24a829f9275f7a65a0fc8ea06ac0fd9e3ad18
  1. .github/
  2. _data/
  3. _includes/
  4. _layouts/
  5. _plugins/
  6. _posts/
  7. contribute/
  8. css/
  9. docs/
  10. download/
  11. getting-started/
  12. img/
  13. js/
  14. scripts/
  15. security/
  16. support/
  17. team/
  18. .asf.yaml
  19. .gitignore
  20. _config-local.yml
  21. _config.yml
  22. CNAME
  23. docker-compose.yml
  24. feed.xml
  25. Gemfile
  26. index.html
  27. LICENSE
  28. NOTICE
  29. README.md
README.md

Apache StormCrawler Website

How to build?

This website is build using Jekyll. Make sure to have it available locally. To build and run server locally type ‘jekyll serve’. The site can then be accessed at localhost:4000.

Docker

You can build the website for local testing by running

docker compose up local

Deployment

This website uses the typical ASF layout. The actual website is found on the branch asf-site, any changes need to be pushed there.

You can run

docker compose up build

which will create a folder _site. This is the content, which needs to be copied after wards to the asf-site branch. If you wish to see a preview for your branch, you can use asf-staging to see a copy hosted under: https://stormcrawler.staged.apache.org/

Build with GitHub actions

The website is automatically build on a push to main and any changes are pushed to the asf-site branch. A preview is available via https://stormcrawler.staged.apache.org/ if you go to the GitHub Actions tab and trigger a manual staging deploy action.