| commit | eb14af5a700aeb279fa141e9e3f03dfd1fcadc8b | [log] [tgz] |
|---|---|---|
| author | Greg Stein <gstein@gmail.com> | Wed Apr 06 01:03:24 2022 -0500 |
| committer | Greg Stein <gstein@gmail.com> | Wed Apr 06 01:03:24 2022 -0500 |
| tree | 99c6e860ea63915c5102e5e4a152cb8a7cbdffcd | |
| parent | f6d7777897bb083e764d47c9d318be579ef9ded3 [diff] |
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.
TBD
$ 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 --notify=somewhere@example.com --theme theme/apache --min-pages=200