Google Git
Sign in
apache / infrastructure-pelican / 588e3a9e773588551d8ed0dba0004579761c53a4
commit588e3a9e773588551d8ed0dba0004579761c53a4[log] [tgz]
authorGreg Stein <gstein@gmail.com>Wed Jul 12 03:19:57 2023 -0500
committerGreg Stein <gstein@gmail.com>Wed Jul 12 03:19:57 2023 -0500
treeafe3378c62f72d20beaa0d07b62ecfdd3d57289d
parenta465c7d4058c0a79bc777594267db5fd49dbd585 [diff]
Provide an argument for pointing to global plugins.

If a pelican site uses the old-style pelicanconf.py, then we
auto-insert some plugins. We also need to auto-insert a path to those
plugins when running locally (the production install on buildbot is
already handled).

Thus: add a new --plugins cmdline argument.

Then add that argument into devtest/compare.sh
2 files changed
tree: afe3378c62f72d20beaa0d07b62ecfdd3d57289d
  1. .github/
  2. bin/
  3. devtest/
  4. plugins/
  5. tests/
  6. .dockerignore
  7. .gitignore
  8. DOCKER.md
  9. Dockerfile
  10. LICENSE
  11. mypy.ini
  12. pelicanconf.md
  13. pylintrc
  14. README.md
  15. requirements.txt
README.md

Title: README

Tools for using Pelican at the ASF

The infrastructure-pelican repository provides a customized process for working with Pelican-based websites at the ASF.

See the getting started guide for working with the ASF Pelican template.

Running Local Preview Builds

See the instructions for local Pelican builds.

Contact users@infra.apache.org for any questions or comments.