|author||Greg Stein <email@example.com>||Wed Apr 06 01:03:24 2022 -0500|
|committer||Greg Stein <firstname.lastname@example.org>||Wed Apr 06 01:03:24 2022 -0500|
More flexible pelican config/run. The current buildsite.py process assumes the content is placed into "content". This is fixed through a new CONTENT_DIR variable. generate_settings() makes some assumptions about the location of the theme and any plugins. Clarify this with SETTINGS_DIR variable. For now, just hack in a look for a "site" directory, which we knows contains all of the above. If a "content" directory is present, then it is the original layout, and we keep on rollin' Added some docco at the head to specify what is needed to run this script in a local dev/test scenario.
$ mkdir /tmp/cm $ cd /tmp/cm $ /path/to/infrastructure-pelican/bin/build-cmark.sh ... (build output here) export LIBCMARKDIR='/tmp/cm/cmark-gfm-0.28.3.gfm.12/lib' $
Copy/paste/execute that printed
export line for use in the following steps.
(of course, you may use any location of your choice;
/tmp/cm is merely an example)
TBD: install a .deb from packages.apache.org
TBD: maybe a macOS variant?
TBD: maybe Windows?
TBD: credentials need to provided in (eg.) bb2.txt
$ ./kick_build.py --repo=www-site --email@example.com --theme theme/apache --min-pages=200